Discovery of federated logins

ABSTRACT

A system includes download location information in an unprotected Uniform Resource Locator (“URL”), where the download location information identifies a download location for downloading an application provided by a cloud system. The system further includes login server information in the unprotected URL, where the login server information identifies a login server that is configured to be logged in before downloading the application from the download location. Based on the unprotected URL, the application is configured to be downloaded on a mobile device from the download location and after logging into the login server. The application may be developed by accessing a web-based application development server in the cloud system, and after the application is developed, the web-based application development server generates the unprotected URL.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority of U.S. Provisional App. No. 62/205,270filed Aug. 14, 2015, entitled “DISCOVERY OF FEDERATED LOGINS,” thedisclosure of which is hereby incorporated by reference.

FIELD

One embodiment is directed generally to an application developmentsystem, and in particular, to a mobile application development system.

BACKGROUND INFORMATION

Generally, ubiquitous mobile services and wireless connections drive thedemand for mobile device applications (commonly referred to as “apps”)for various personal and business needs. Such demand in turn leads tothe desirability of mobile application development platforms/means thatsimplify and expedite mobile application development and modification,while also allowing for sophisticated application features and ensuringthat business security is not compromised.

SUMMARY

One embodiment is a system that includes download location informationin an unprotected Uniform Resource Locator (“URL”), where the downloadlocation information identifies a download location for downloading anapplication provided by a cloud system. The system further includeslogin server information in the unprotected URL, where the login serverinformation identifies a login server that is configured to be logged inbefore downloading the application from the download location. Based onthe unprotected URL, the application is configured to be downloaded on amobile device from the download location and after logging into thelogin server. The application may be developed by accessing a web-basedapplication development server in the cloud system, and after theapplication is developed, the web-based application development servergenerates the unprotected URL.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a system for developing applications thatuse mobile cloud services, in accordance with an embodiment of thepresent invention.

FIG. 2 is a block diagram of a computing environment to facilitatecommunication between a mobile computing device and enterprise computersystems according to some embodiments of the present invention.

FIG. 3 illustrates a mobile application springboard in accordance withan embodiment of the present invention.

FIGS. 3A and 3B illustrate a mobile application user interface (“UI”) inaccordance with an embodiment of the present invention.

FIG. 4 is a block diagram of a mobile application framework runtimearchitecture in accordance with embodiments of the present invention.

FIG. 5 is a block diagram of a system for developing mobile applicationsin a mobile cloud infrastructure in accordance with embodiments of thepresent invention.

FIG. 6 is a block diagram of network components in a system for buildingmobile applications in accordance with embodiments of the presentinvention.

FIG. 7 is a block diagram of mobile security suite components inaccordance with embodiments of the present invention.

FIG. 8 is a flow diagram of mobile application development in accordancewith embodiments of the present invention.

FIG. 9 is an example application network topology for web basedapplication development in accordance with embodiments of the presentinvention.

FIG. 10 is an example application sharing flow in accordance withembodiments of the present invention.

FIG. 11 is a flow diagram of federated login discovery functionality inaccordance with embodiments of the present invention.

DETAILED DESCRIPTION

An application refers to a software program, which on execution performsspecific desired tasks. In general, several applications are executed ina run-time environment containing one or more operating systems (“OSs”),virtual machines (e.g., supporting Java™ programming language), devicedrivers, etc. Developers often use Application Development Frameworks(“ADFs”) (which are by themselves applications) forimplementing/developing desired applications. An ADF provides a set ofpre-defined code/data modules that can be directly/indirectly used inthe development of an application. An ADF is an example of an integrateddevelopment environment (“IDE”) that can include code generators,debuggers, etc. In general, an ADF simplifies application development byproviding re-usable components which can be used by applicationdevelopers to define user interfaces (“UIs”) and application logic by,for example, selecting components to perform desired tasks and definingthe appearance, behavior, and interactions of the selected components.Some ADFs, such as “Oracle ADF” from Oracle Corp., are based on amodel-view-controller (“MVC”) design pattern that promotes loosecoupling and easier application development and maintenance.

Generally, many companies have expressed the need to allow theiremployees to access secure enterprise applications with mobile devicesfrom off-site locations, so that on-the-go employees can accessinformation that is stored on enterprise computer systems. With suchcapabilities, salespeople may work from the road, service techniciansmay look up parts while at a customer site, employees may work fromhome, etc. Some companies would also like to allow end customers toaccess data located in enterprise computer systems. Such access maydifferentiate a company from competitors by improving the customerexperience and lowering costs. For example, by implementing such access,a store may allow customers to remotely search store inventory for anitem and shop whenever convenient, thereby improving customer experienceand lowering the need for salespeople, operators, and other staff.

Different enterprise application vendors have traditionally fulfilledthis need by offering specialized portals in combination with eithercompany owned secure mobile devices or custom mobile applications.However, with the current explosion in the variety of available personalmobile devices, these traditional solutions quickly become obsoletesince vendors simply cannot keep up with all the latest OSs and hardwarethat become available.

Further, an application may need to connect and synchronize withdifferent enterprise computer systems depending on the application typeand/or the type of data used by the application. These enterprisecomputer systems may be supported by different backend computer systemswhich may also vary based on application type and data type. However,different backend enterprise systems may use different communicationprotocols and mechanisms to communicate data to devices, thereby causingmobile computing devices that run a variety of applications to encounterchallenges for communicating with different backend computer systemsthat support an enterprise computer system.

Yet further, security may become a concern in allowing access tointernal computer systems of an enterprise. The differences incommunication protocols supported between the mobile computing devicesand the enterprise computer systems may further complicate securityaccess management for communications between mobile computing devicesand enterprise computer systems. For example, different mechanisms maybe implemented to ensure authentication of an application to access aparticular enterprise computer system that has a proprietary securityprotocol. Some known systems have attempted to address this issues byconnecting off-the-shelf consumer mobile devices with backend enterprisesystems of companies. These devices may be configured with applicationsor OSs that connect to an enterprise network through special portalsdedicated to communication with enterprise backend computer systems.However, manufacturers of mobile devices, application developers, andenterprises may benefit from more flexible and robust techniques fordeveloping applications and connecting mobile devices to enterprisebackend computer systems.

In contrast to the known systems, embodiments of the present inventionprovide a declarative browser based client application development toolfor rapid business user friendly mobile application composition in a“cloud” service. In one embodiment, the cloud service is “Mobile CloudService” (“MCS”) from Oracle Corp. Embodiments allow for building mobileapplications using pre-defined templates that use the cloud service forbackend services, so that a service definition can be presented to adeveloper during application development to allow for rapid connectionbetween UI design and backend services.

MCS

In embodiments that use MCS, MCS facilitates communication between amobile computing device and enterprise computer systems via a cloudcomputer system. MCS uses a third party cloud based interface betweenmobile devices and an enterprise network of a company. The cloud basedinterface centralizes secure adaptors for various enterprise computersystems, and translates different protocols to a standardizedRepresentational State Transfer (“REST”) architecture. Companies can useembodiments of the present invention to create their own custom mobileapplications using available tools on MCS, and such applications can bedownloaded in native form onto mobile user devices. Once an applicationis installed, it can access the cloud based interface of MCS to reachvarious enterprise computer systems through the secure adaptors providedby MCS.

For application development in embodiments that use MCS, MCS providesbackend services under the Mobile Backend as a Service (“MBaaS,” alsoreferred to as “BaaS”) model. MBaaS allows Web and mobile applicationdevelopers to link their applications to backend cloud storage and APIsexposed by backend applications while also providing user management,push notifications, integration with social networking services, etc. Byusing backend services provided in MCS under the MBaaS model,embodiments provide a declarative Web-based UI configured for mobileapplication development by non-technical users with no familiarity withcoding.

In one embodiment, a wizard is launched when a user starts developing anew application, and the user is asked to give a name and descriptionfor the new application. Then, the user is asked to design the firstpage of the application by selecting from a set of pre-defined templates(e.g., tabs, bottom tabs, pagination, etc.) that can pre-seed the UI forthe first page. The UI is then completed by specifying details in thetemplate, while a preview is automatically updated to show the changes.Upon completing the UI design, the user can use a palette to browse acatalog of available services and data sources that are available to themobile application through MCS (e.g., a service catalog). For each itemof the catalog that is added to the UI, the user is presented with alist of attributes, and using one or more gestures (e.g., drag and drop,etc.) the user can bind the attributes to UI elements. The user canrepeat the process of feature definition and data-binding to create amobile application. Other UI components such as maps, graphs, etc., canalso be added to the UI. When the application is ready for testing, theuser may publish the application so that corresponding binaries arecreated (building native executables for iOS, Android, or any othermobile device OS), and a Quick Response (“QR”) code is subsequentlygenerated and provided to the user. If the user scans the QR code by amobile device, the application is installed over the air onto the mobiledevice.

Embodiments use pre-built components in an ADF. The components offerdata interaction, data visualization, and encapsulated browser sideoperations, and simplify rich client application development. ADF mayalso implement a plugin such as Apache Cordova plugin to access devicefeatures such as a camera, Global Positioning System (“GPS”), contacts,etc.

In one embodiment, when an ADF receives a request to build anapplication for a mobile device, it determines portions of one or morealready developed applications that have been precompiled using atoolkit, and modifies declarative information associated with thoseexisting applications. This embodiment then builds the requestedapplication based on the modified declarative information and one ormore binary artifacts of the existing applications by packaging thebinary artifacts representing the requested application for a desiredoperating system (“OS,” such as iOS, Android, etc.). The ADF thencompiles the requested application to generate one or more binaryartifacts and a set of definition files. In end-user development, anartifact is an application or a complex data object that is created byan end-user without the need to know a programming language.

Mobile Security

Some embodiments use security services provided by a mobile securitysuite such as “Oracle Mobile Security Suite” (“OMSS”) from Oracle Corp.OMSS is a mobile device and mobile application security solution thatprovides an employee-centric, comprehensive Enterprise MobilityManagement (“EMM”) solution and a consumer-centric mobile and socialservice. EMM provides mobile device management (“MDM”), mobileapplication management (“MAM”), mobile content management (“MCM”), andmobile identity policies by seamlessly tying to existing user identitiesand leveraging advanced features of the enterprise backend identitymanagement infrastructure for mobile access. Security policies, adheringto corporate needs, can be defined to enforce a complete device lockdown (typically for corporate owned devices) and/or to separate personalapplications from secure “containerized” corporate applications and data(for bring your own device (“BYOD”) cases). A mobile and social serviceprovides a software development kit (“SDK”) allowing corporatedevelopers to secure custom enterprise applications for iOS and Androiddevices, bridging the gap between mobile devices, social networks, andenterprise backend identity management infrastructure.

OMSS delivers a secure container to a mobile device for application andcontent security to separate, protect, and wipe corporate applicationsand data. All communication between the mobile device and enterpriseintranet resources goes through an authenticated transport layersecurity (“TLS”)/secure socket layer (“SSL”) tunnel (“AppTunnel”) thatcan only be used by vetted (or “containerized”) applications of themobile device. The AppTunnel is terminated at a Mobile Security AccessServer located at the corporate demilitarized zone (“DMZ”). This serveroffers secure Intranet access to mobile devices and terminates only theAppTunnel from the secure container, thereby lessening the risk of rogueapplications and the need for device level VPN.

Leveraging what is provided by an ADF, embodiments provide browser basedapplication development, which does not require coding and which easilymaps to business services. Embodiments also allow for previewing anapplication inline (e.g., as the application is being developed), aswell as editing, testing, and publishing an application from a browser.Accordingly, instead of an IDE such as “Jdeveloper” from Oracle Corp.that is configured for use by professional developers, embodiments areconfigured for use by business users (e.g., non-technical users).

Service Catalog

To support embodiments of the present invention that use MCS, MCSprovides access to an API catalog such as “Oracle API Catalog” (“OAC”)from Oracle Corp. OAC provides visibility to available APIs in anorganization so those APIs may be reused for application development.OAC includes a simple metamodel for an API asset, automation to populateOAC with APIs, and the ability for users to search OAC for APIs andunderstand the details of the APIs to assess their fit in theirapplications. OAC includes a harvester that creates API assets in OAC.In some embodiments, harvesting is performed at build time of projects.The harvester introspects deployed services and creates API assetsrepresenting services discovered in the project such as service orientedarchitecture (“SOA”) Services and Service Bus proxies, Web ServicesDescription Language (“WSDL”) based Web services, and Web ApplicationDescription Language (“WADL”) based REST services. The created assetsare collected in OAC.

After the API assets are created by the harvester, curators edit the APIassets using a simple editor to provide additional metadata tofacilitate the discovery and understanding of the APIs. Curators canchange the name, add a description, tag keywords, or add documentreferences to the API assets in OAC. This metadata simplifies discoveryand understanding of each API asset by a user. After the API metadata isedited, curators publish the API by making it visible to users in OAC.Published assets are available in the OAC console and via the OracleJDeveloper Oracle Enterprise Repository plug-in. Users can search OAC todiscover APIs and review the metadata provided by the curator to learnmore about an API.

Each OAC user is assigned a role which determines which OAC features andcontent are available for each user. There are predefined roles in OACincluding developer, curator, and admin. Users with the developer rolehave the ability to search OAC for published APIs, examine the APImetadata to better understand the API, declare interest in the API, andsubmit ratings and reviews for an API. In addition to the capabilitiesavailable to the developer role, users with the curator role can run theharvester to create new API assets in OAC, edit the APIs to update theirmetadata, and publish them. In addition to the capabilities available tocurators and developers, users with the admin role have access to anAdmin page in OAC to administer the infrastructure of OAC by editingsystem settings, creating new users, creating new departments, managingsessions, and using the import/export tool. Admins can also configuresecurity features included with OAC.

In some embodiments, an application may be developed and deployed to amobile device as either a native application or a hosted application.For native application deployment, a complete application is installedon the device. For hosted application development, a user needs todownload a hosting application from an “app store,” where such hostingapplication “hosts” the hosted applications that will be installed as“features” onto the hosting application. This embodiment may allow forupdating a running hosting application from a server, such thatdeclarative metadata can be sent to the device and overlaid on top ofthe existing application to update the application to run against thisnew metadata.

FIG. 1 is a block diagram of a system environment 100 for developingapplications by using pre-defined templates that allow for use of MCS122 as backend services. A service definition can be presented to a userduring application development allowing rapid connection between UIdesign and backend services.

In the illustrated embodiment, system environment 100 includes cloudinfrastructure system 102 that provides cloud services to one or moreclient computing devices 104, 106, and 108. Client computing devices104, 106, and 108 may be used by users to interact with cloudinfrastructure system 102. Client computing devices 104, 106, and 108may be configured to operate a client application such as a Web browser,a proprietary client application (e.g., Oracle Forms), or some otherapplication, which may be used by a user of the client computing deviceto interact with cloud infrastructure system 102 to use servicesprovided by cloud infrastructure system 102.

Cloud infrastructure system 102 may have other components than thosedepicted. Further, the embodiment shown in FIG. 1 is only one example ofa cloud infrastructure system that may incorporate an embodiment of theinvention. In some other embodiments, cloud infrastructure system 102may have more or fewer components than shown in FIG. 1, may combine twoor more components, or may have a different configuration or arrangementof components.

Client computing devices 104, 106, and 108 may be portable handhelddevices (e.g., an iPhone®, cellular telephone, an iPad®, computingtablet, a personal digital assistant (“PDA”)) or wearable devices (e.g.,a Google Glass® head mounted display), running software such asMicrosoft Windows Mobile®, and/or a variety of mobile OSs such as iOS,Windows Phone, Android, BlackBerry 10, Palm OS, and the like, and beingInternet, e-mail, short message service (“SMS”), Blackberry®, or othercommunication protocol enabled. Client computing devices 104, 106, and108 can be general purpose personal computers including, by way ofexample, personal computers and/or laptop computers running variousversions of Microsoft Windows®, Apple Macintosh®, and/or Linux OSs.Client computing devices 104, 106, and 108 can be workstation computersrunning any of a variety of commercially-available UNIX® or UNIX-likeOSs, including without limitation the variety of GNU/Linux OSs, such asfor example, Google Chrome OS. Alternatively, or in addition, clientcomputing devices 104, 106, and 108 may be any other electronic device,such as a thin-client computer, an Internet-enabled gaming system (e.g.,a Microsoft Xbox gaming console with or without a Kinect® gesture inputdevice), and/or a personal messaging device, capable of communicatingover network(s) 110.

Although exemplary system environment 100 is shown with three clientcomputing devices, any number of client computing devices may besupported. Other devices such as devices with sensors, etc., mayinteract with cloud infrastructure system 102.

Network(s) 110 may facilitate communications and exchange of databetween clients 104, 106, and 108 and cloud infrastructure system 102.Network(s) 110 may be any type of network familiar to those skilled inthe art that can support data communications using any of a variety ofcommercially-available protocols, including without limitationtransmission control protocol/Internet protocol (“TCP/IP”), systemsnetwork architecture (“SNA”), Internet packet exchange (“IPX”),AppleTalk, etc. Merely by way of example, network(s) 110 can be a localarea network (“LAN”), such as one based on Ethernet, Token-Ring and/orthe like. Network(s) 110 can be a wide-area network and the Internet. Itcan include a virtual network, including without limitation a virtualprivate network (“VPN”), an intranet, an extranet, a public switchedtelephone network (“PSTN”), an infra-red network, a wireless network(e.g., a network operating under any of the Institute of Electrical andElectronics (“IEEE”) 802.11 suite of protocols, Bluetooth®, and/or anyother wireless protocol); and/or any combination of these and/or othernetworks.

Cloud infrastructure system 102 may comprise one or more computersand/or servers. These computer systems or servers may be composed of oneor more general purpose computers, specialized server computers(including, by way of example, personal computer (“PC”) servers, UNIX®servers, mid-range servers, mainframe computers, rack-mounted servers,etc.), server farms, server clusters, or any other appropriatearrangement and/or combination. In various embodiments, one or morecomputer systems or servers associated with cloud infrastructure system102 may be adapted to run one or more services or software applicationsdescribed in the foregoing disclosure. For example, one or more computersystems or servers associated with cloud infrastructure system 102 maycorrespond to a server for performing processing described hereinaccording to an embodiment of the present disclosure.

One or more computer systems or servers associated with cloudinfrastructure system 102 may run an OS including any of those discussedabove, as well as any commercially available server OS. One or morecomputer systems or servers associated with cloud infrastructure system102 may also run any of a variety of additional server applicationsand/or mid-tier applications, including hypertext transport protocol(“HTTP”) servers, file transfer protocol (“FTP”) servers, common gatewayinterface (“CGI”) servers, JAVA® servers, database servers, and thelike.

In certain embodiments, services provided by cloud infrastructure system102 may include a host of services that are made available to users ofcloud infrastructure system 102 on demand, such as online data storageand backup solutions, Web-based e-mail services, hosted office suitesand document collaboration services, database processing, managedtechnical support services, and the like. Services provided by cloudinfrastructure system 102 can dynamically scale to meet the needs of itsusers. A specific instantiation of a service provided by cloudinfrastructure system 102 is referred to herein as a “service instance.”In general, any service made available to a user via a communicationnetwork, such as the Internet, from a cloud service provider's system isreferred to as a “cloud service.” Typically, in a public cloudenvironment, servers and systems that make up the cloud serviceprovider's system are different from the customer's own on-premisesservers and systems. For example, a cloud service provider's system mayhost an application, and a user may, via a communication network such asthe Internet, on demand, order and use the application.

In some examples, a service instance instantiated by cloudinfrastructure 102 may include protected computer network access tostorage, a hosted database, a hosted Web server, a software application,or other service provided by a cloud vendor to a user, or as otherwiseknown in the art. For example, a service instance instantiated by cloudinfrastructure 102 can include password-protected access to remotestorage on the cloud through the Internet. As another example, a serviceinstance instantiated by cloud infrastructure 102 can include a Webservice-based hosted relational database and a script-languagemiddleware engine for private use by a networked developer. As anotherexample, a service instance instantiated by cloud infrastructure 102 caninclude access to an email software application hosted on a cloudvendor's Web site.

In certain embodiments, cloud infrastructure system 102 may include asuite of applications, middleware, development service, and databaseservice offerings that are delivered to a customer in a self-service,subscription-based, elastically scalable, reliable, highly available,and secure manner. An example of such a cloud infrastructure system asembodied in cloud infrastructure service 102 is “Oracle Public Cloud”from Oracle Corp.

Cloud infrastructure system 102 may provide the cloud services viadifferent deployment models. For example, services may be provided undera public cloud model in which cloud infrastructure system 102 is ownedby an organization selling cloud services (e.g., owned by Oracle Corp.)and the services are made available to the general public or differentindustry enterprises. As another example, services may be provided undera private cloud model in which cloud infrastructure system 102 isoperated solely for a single organization and may provide services forone or more entities within the organization. The cloud services mayalso be provided under a community cloud model in which cloudinfrastructure system 102 and the services provided by cloudinfrastructure system 102 are shared by several organizations in arelated community. The cloud services may also be provided under ahybrid cloud model, which is a combination of two or more differentmodels.

In some embodiments, the services provided by cloud infrastructuresystem 102 may include one or more services provided under software as aservice (“SaaS”) category, platform as a service (“PaaS”) category,infrastructure as a service (“IaaS”) category, MBaaS category, or othercategories of services including hybrid services. In some embodiments,the services provided by cloud infrastructure system 102 may include,without limitation, application services, platform services,infrastructure services, backend services, etc. In some examples,application services may be provided by cloud infrastructure system 102via a SaaS platform. The SaaS platform may be configured to providecloud services that fall under the SaaS category. For example, the SaaSplatform may provide capabilities to build and deliver a suite ofon-demand applications on an integrated development and deploymentplatform. The SaaS platform may manage and control the underlyingsoftware and infrastructure for providing the SaaS services. Byutilizing the services provided by the SaaS platform, customers canutilize applications executing on the cloud infrastructure system.Customers can acquire the application services without the need forcustomers to purchase separate licenses and support. Various differentSaaS services may be provided. Examples include, without limitation,services that provide solutions for sales performance management,enterprise integration, and business flexibility for largeorganizations.

In some embodiments, platform services may be provided by cloudinfrastructure system 102 via a PaaS platform. The PaaS platform may beconfigured to provide cloud services that fall under the PaaS category.Examples of platform services may include without limitation servicesthat enable organizations (such as Oracle) to consolidate existingapplications on a shared, common architecture, as well as the ability tobuild new applications that leverage the shared services provided by theplatform. The PaaS platform may manage and control the underlyingsoftware and infrastructure for providing the PaaS services. Customerscan acquire the PaaS services provided by cloud infrastructure system102 without the need for customers to purchase separate licenses andsupport. Examples of platform services include, without limitation,“Oracle Java Cloud Service” (“JCS”) from Oracle Corp., “Oracle DatabaseCloud Service” (“DBCS”) from Oracle Corp., and others.

By utilizing the services provided by the PaaS platform, customers canemploy programming languages and tools supported by cloud infrastructuresystem 102 and also control the deployed services. In some embodiments,platform services provided by cloud infrastructure system 102 mayinclude database cloud services, middleware cloud services (e.g., OracleFusion Middleware services), and Java cloud services. In one embodiment,database cloud services may support shared service deployment modelsthat enable organizations to pool database resources and offer customersa Database as a Service in the form of a database cloud. Middlewarecloud services may provide a platform for customers to develop anddeploy various business applications, and Java cloud services mayprovide a platform for customers to deploy Java applications, in thecloud infrastructure system.

Various different infrastructure services may be provided by an IaaSplatform in cloud infrastructure system 102. The infrastructure servicesfacilitate the management and control of the underlying computingresources, such as storage, networks, and other fundamental computingresources for customers utilizing services provided by the SaaS platformand the PaaS platform.

In certain embodiments, cloud infrastructure system 102 may providecomprehensive management of cloud services (e.g., SaaS, PaaS, IaaS, andMBaaS services) in the cloud infrastructure system. In one embodiment,cloud management functionality may include capabilities forprovisioning, managing and tracking a customer's subscription receivedby cloud infrastructure system 102, and the like. In variousembodiments, cloud infrastructure system 102 may be adapted toautomatically provision, manage and track a customer's subscription toservices offered by cloud infrastructure system 102. A customer, via asubscription order, may order one or more services provided by cloudinfrastructure system 102. Cloud infrastructure system 102 then performsprocessing to provide the services in the customer's subscription order.

In one embodiment, cloud management functionality may be provided by oneor more modules, such as order management and monitoring module 114.These modules may include or be provided using one or more computersand/or servers, which may be general purpose computers, specializedserver computers, server farms, server clusters, or any otherappropriate arrangement and/or combination.

In exemplary operation, a customer using client computing devices 104,106 or 108, may interact with cloud infrastructure system 102 byrequesting one or more services provided by cloud infrastructure system102. The customer may issue service request 134 cloud infrastructuresystem 102 using a variety of means. Service request 134 may includeplacing an order for a subscription for one or more services offered bycloud infrastructure system 102, accessing one or more services offeredby cloud infrastructure system 102, or the like. In certain embodiments,the customer may access a cloud UI 132, 134, 138, and place asubscription order via these UIs. The order information received bycloud infrastructure system 102 in response to the customer placing anorder may include information identifying the customer and one or moreservices offered by the cloud infrastructure system 102 to which thecustomer intends to subscribe. After an order has been placed by thecustomer, the order information is received via cloud UIs, 132, 134,and/or 138.

In this example, order management and monitoring module 112 sendsinformation received from a customer to an order database to have theorder placed by the customer stored. The order database can be one ofseveral databases operated by cloud infrastructure system 102 andoperated in conjunction with other system elements. Order management andmonitoring module 112 may forward information that includes all or partof the order information stored in the order database to an ordermanagement module. In some instances, the order management module may beconfigured to perform billing and accounting functions related to theorder, such as verifying the order, and upon verification, booking theorder.

In certain embodiments, cloud infrastructure system 100 may includeidentity management module 114. Identity management module 114 may beconfigured to provide identity services, such as access management andauthorization services in cloud infrastructure system 102. In someembodiments, identity management module 114 may control informationabout customers who wish to utilize the services provided by cloudinfrastructure system 102. Such information can include information thatauthenticates the identities of such customers and information thatdescribes which actions those customers are authorized to performrelative to various system resources (e.g., files, directories,applications, communication ports, memory segments, etc.) Identitymanagement module 114 may also include the management of descriptiveinformation about each customer and about how and by whom thatdescriptive information can be accessed and modified.

In certain embodiments, cloud infrastructure system 102 may also includeinfrastructure resources 116 for providing the resources used to providevarious services to customers of cloud infrastructure system 102. In oneembodiment, infrastructure resources 116 may include pre-integrated andoptimized combinations of hardware, such as servers, storage, andnetworking resources to execute the services provided by the PaaSplatform and the SaaS platform.

In some embodiments, resources in cloud infrastructure system 102 may beshared by multiple users and dynamically re-allocated per demand.Additionally, resources may be allocated to users in different timezones. For example, cloud infrastructure system 102 may enable a firstset of users in a first time zone to utilize resources of the cloudinfrastructure system for a specified number of hours and then enablethe re-allocation of the same resources to another set of users locatedin a different time zone, thereby maximizing the utilization ofresources.

In certain embodiments, a number of internal shared services 118 may beprovided that are shared by different components or modules of cloudinfrastructure system 102 and by the services provided by cloudinfrastructure system 102. These internal shared services 118 mayinclude, without limitation, a security and identity service, anintegration service, an enterprise repository service, an enterprisemanager service, a virus scanning and white list service, a highavailability, backup and recovery service, service for enabling cloudsupport, an email service, a notification service, a file transferservice, and the like.

In certain embodiments, a number of external shared services 120 may beprovided that are shared by different components or modules of cloudinfrastructure system 102 and by the services provided by cloudinfrastructure system 102. These external shared services 120 mayinclude, without limitation, a security and identity service, anintegration service, an enterprise repository service, an enterprisemanager service, a virus scanning and white list service, a highavailability, backup and recovery service, service for enabling cloudsupport, an email service, a notification service, a file transferservice, and the like.

In various embodiments, external shared services 120 may include one ormore components that provide access, data transformation, automation, orthe like to enterprise computer system(s) 126. Access to enterprisecomputer system(s) 126 may be shared by different components or modulesof cloud infrastructure system 102 and by the services provided by cloudinfrastructure system 102. In some embodiments, access to enterprisecomputer system(s) 126 may be shared by service instances provided bycloud infrastructure system 102 that are restricted to one or moresubscribers.

In further embodiments, external shared services 120 may includeexternal application programming interface (“API”) services 128 that areshared by different components or modules of cloud infrastructure system102 and by the services provided by cloud infrastructure system 102.These external API services 128 may include, without limitation, APIsprovided by other third party services or entities.

Various different mobile cloud services may be provided by MCS 122 incloud infrastructure system 102. MCS 122 facilitates communicationbetween a mobile computing device and enterprise computer systems (e.g.,enterprise computer systems 124 and 126) according to some embodimentsof the present invention. MCS 122 may include one or more memory storagedevices (“local storage”) used to store enterprise data andauthentication information. Enterprise data may be received fromenterprise computer systems 126 or from client computing devices 104,106, or 108 or may include enterprise data converted by cloudinfrastructure system 102, or combinations thereof. Authenticationinformation may be received from identity management system 116 and/orgenerated by cloud infrastructure system 102. In some embodiments,authentication information may include information indicating securityauthentication of a user with regard to a request for a service.

Enterprise computer systems, such as enterprise computer systems 126 maybe physically located beyond a firewall of cloud infrastructure system102 at a different geographic location (e.g., remote geographiclocation) than cloud infrastructure system 102. In some embodiments,enterprise computer systems 126 may include one or more differentcomputers or servers. In some embodiments, enterprise computer systems126 may be part of a single computer system.

In certain embodiments, enterprise computer systems 126 may communicatewith cloud infrastructure system 102 using one or more differentprotocols. Each of enterprise computer systems 126 may communicate withcloud infrastructure system 102 using a different communicationprotocols. Enterprise computer systems 126 may support the same ordifferent security protocols. In some embodiments, MCS 122 may includean agent system to handle communication with enterprise computer systems126.

A protocol may include a communication protocol, such as SPeeDY(“SPDY”). A protocol may include an application protocol such as anHTTP-based protocol. In some embodiments, enterprise computer systems126 may communicate with cloud infrastructure system 102 using acommunication protocol such as REST or Simple Object Access Protocol(“SOAP”). For example, REST protocol may support a formats includinguniform resource identifier (“URI”) or uniform resource locator (“URL”).Enterprise Data formatted for communication using REST protocol may beeasily converted to data formats such as JavaScript Object Notation(“JSON”), comma-separated values (“CSV”), and really simple syndication(“RSS”). Enterprise computer systems 126 and cloud infrastructure system102 may communicate using other protocols such as remote procedure calls(“RPC”) (e.g., extended markup language (“XML”) RPC).

In some embodiments, MCS 122 may include an adaptor interface configuredto support communication with one or more services provided by cloudinfrastructure service 102, some of which may support differentprotocols or techniques for communications. In some embodiments, MCS 122may include an adaptor interface configured to support communicationwith enterprise computer systems 126, some of which may supportdifferent protocols or techniques for communications. MCS 122 mayinclude one or more adaptors each of which may be configured tocommunicate according to a communication protocol, a type of enterprisecomputer system, a type of application, a type of service, orcombinations thereof. A communication protocol supported by an adaptormay be specific to a service or one or more of enterprise computersystems 126.

In certain embodiments, client computing devices 104, 106, and 108 mayeach implement an application that can provide specific UIs tocommunicate with MCS 122. A specific UI may be configured to communicateusing a specific communication protocol. In some embodiments, specificUIs may include callable interfaces, functions, routines, methods,and/or operations that may be invoked to communicate with MCS 122.Specific UIs may accept as input parameters for communicating with aservice provided by cloud infrastructure service 102 or with enterprisecomputer systems 126 for enterprise data and/or to request a service. Insome embodiments, communication through MCS 122 may be converted forcommunication using a custom communication protocol. In someembodiments, specific UIs may correspond to a custom client in anapplication.

MCS 122 may include one or more callable interfaces, e.g., an API.Callable interfaces associated with MCS 122 may enable an application ona mobile computing device to communicate requests to MCS 122. Callableinterfaces associated with MCS 122 may support a common or standardinterface, which may allow requests including their parameters to bereceived from apps according to a standardized protocol, architecturalstyle, and/or format (e.g., a REST protocol). Callable interfacesassociated with MCS 122 may be configurable by a user of any one ofcomputing devices 104, 106, or 108. Callable interfaces associated withMCS 122 may receive requests for services according to a communicationprotocol. Device application developers can connect to MCS 122 for theircustom applications. In some embodiments, a callable interfaceassociated with MCS 122 may be configured by the same person thatdevelops an app, such that the person can implement a custom applicationto communicate with MCS 122.

Callable interfaces associated with MCS 122 may further enableenterprise computer systems 126 to communicate with MCS 122 according toa standardized protocol or format. Similar to application developers,those who manage enterprise computer systems can implement code (e.g.,an agent system) that is configured to communicate with MCS 122 via oneor more callable interfaces. Callable interfaces associated with MCS 122may be implemented based on a type of a computing device, a type ofenterprise computer systems, an app, an agent system, a service, aprotocol, or other criterion. In some embodiments, callable interfacesassociated with MCS 122 may support requests for services includingauthentication, compression, encryption, pagination with cursors,client-based throttling, non-repudiation, logging, and metricscollection. In some embodiments, callable interfaces associated with MCS122 may be implemented for custom business-related services, such asauthentication, policy enforcement, caching of responses, throttling ofcalls to MCS 122, translation between asynchronous and synchronouspatterns, logging of calls to underlying services, or combinationsthereof. In some embodiments, callable interfaces associated with MCS122 may enable users to load custom code for implementation by cloudinfrastructure system 102. The custom code may implement one or morecallable interfaces associated with MCS 122 for cloud infrastructuresystem 102, which can enable users to access custom services or otherenterprise computer systems.

Protocol translators associated with MCS 122 may process a message todetermine a communication protocol for a message and/or to convert amessage to a communication protocol for a destination. Protocoltranslators associated with MCS 122 may convert a request received fromclient computing devices 104, 106, or 108. The request may be convertedfrom a format of a communication protocol supported by client computingdevices 104, 106, or 108 to a format of a communication protocolsupported by a service provided by cloud infrastructure service 102 orenterprise computer systems 126. Protocol translators associated withMCS 122 may convert a response received from a service provided by cloudinfrastructure service 102 or enterprise computer systems 126. Aresponse may be converted from a format of a communication protocolsupported by a service provided by cloud infrastructure service 102 orenterprise computer systems 126 to a format of a communication protocolsupported by client computing devices 104, 106, or 108.

Security services associated with MCS 122 may manage securityauthentication for requests received from any of client computingdevices 104, 106, or 108. Security services associated with MCS 122 mayprotect the integrity of customer processes and enterprise data. Toprevent system or data from being compromised, security authenticationmay occur when a request is received from client computing devices 104,106, or 108. Security authentication may be performed before a requestis dispatched for processing by cloud infrastructure system 102. Thesecurity authentication determined for a user may enable a userassociated with a mobile computing device to have authorization torequest services via MCS 122. The security authentication may reduceefforts for a user to authenticate for different requests and/orservices requested via MCS 122. Security services associated with MCS122 may be implemented as one or more functional blocks or modulesconfigured to perform various operations authenticating security of arequest.

Authentication services associated with MCS 122 may manage securityauthentication for requests received from client computing devices 104,106, or 108. Authentication services associated with MCS 122 maydetermine security authentication for a user associated with a computingdevice that sends a request to MCS 122. Security authentication may bedetermined based on a time period, which may be tied to operation of anapplication (e.g., launching an application), a request, a computingdevice, an enterprise computer system, other criterion related to arequest, or combinations thereof. Security authentication may beverified and granted for any one of the following, such as an individualrequest, one or more enterprise computer systems, a particular service,a type of service, a user, a computing device, other criterion fordetermining security authentication, or combinations thereof. In someembodiments, cloud infrastructure system 102 may store authenticationinformation of users received from enterprise computer systems orauthentication systems supporting enterprise computer systems. Cloudinfrastructure system 102 may determine authentication by performing alookup function to determine whether an identity of a user associatedwith a request has authority to make such a request. The storedauthentication information may include information such as the type ofrequests, functions, enterprise computer systems, enterprise data, orthe like that a user may be authorized to access. In some embodiments,infrastructure system 102 may initiate communication with a requestingcomputing device to determine authentication.

In some embodiments, security authentication may be determined based ona role associated with a user requesting a service. The role may beassociated with a user requesting access to MCS 122. In someembodiments, a user may request services as a subscriber or tenant ofMCS 122 who may be granted access to resources and/or services providedby MCS 122. Authentication may correspond to a user's subscription toMCS 122, such that a user may be authorized to request services via MCS122 as a subscriber. In some embodiments, the subscription may belimited to a particular set of resources provided by MCS 122. Securityauthentication may be based on the resources and/or services accessibleto the user of MCS 122. In some embodiments, a request may beprovisioned a template during execution called a “runtime environment.”The runtime environment may be associated with resources that areallocated for a request, a user, or a device.

In some embodiments, authentication services associated with MCS 122 mayrequest an identity management system to determine securityauthentication for the user. The identity management system may beimplemented by cloud infrastructure system 102 (e.g., as identitymanagement 114) or by another computer system that is external to cloudinfrastructure system 102. Identity management 116 may determinesecurity authentication of the user based on the user's role orsubscription for accessing MCS 122. The role or subscription may beassigned privileges and/or entitlements with respect to an enterprisecomputer system, a service provided by an enterprise computer system, afunction or feature of an enterprise computer system, other criterionfor controlling access to an enterprise computer system, or combinationsthereof.

ADF

Various different ADFs 124 may be provided in cloud infrastructuresystem 102. ADFs 124 provide the infrastructure code to implement agileSOA based applications. ADFs 124 further provide a visual anddeclarative approach to development through one or more developmenttools (e.g., “Oracle JDeveloper 11g” development tool). One or moreframeworks provided by ADFs 124 may implement an MVC design pattern.Such frameworks offer an integrated solution that covers all the layersof the MVC architecture with solutions to such areas asObject/Relational mapping, data persistence, reusable controller layer,rich Web UI framework, data binding to UI, security and customization.Extending beyond the core Web based MVC approach, such frameworks alsointegrate with the Oracle SOA and WebCenter Portal frameworkssimplifying the creation of complete composite applications.

In certain embodiments, ADFs 124 make it easy to develop agileapplications that expose data as services by coupling a serviceinterface to built-in business services provided by cloud infrastructuresystem 102. This separation of business service implementation detailsis performed in ADFs 124 via metadata. Use of this metadata-drivenarchitecture enables application developers to focus on the businesslogic and user experience, rather than the details of how services areaccessed. In certain embodiments, ADFs 124 store implementation detailsof services in metadata in a model layer. This enables developers toexchange services without modifying the UI, making the applicationextremely agile. Additionally, the developer creating the UI does notneed to bother with business service access details. Instead, developerscan focus on developing the application interface and interaction logic.Creating the user experience can be as simple as dragging-and-droppingthe desired business services onto a visual page designer and indicatingwhat type of component should represent that data.

In various embodiments, developers interact with ADFs 124 to createmodules forming enterprise applications. The enterprise applications canbe executed within the context of cloud infrastructure system 102. Invarious embodiments, developers interact with ADFs 124 to create modulesforming mobile applications. The mobile applications can be executedwithin the context of cloud infrastructure system 102. Features of thepresent invention described below may be implemented using any desiredcombination of programming language and application developmentframework as will be apparent to one skilled in the relevant arts byreading the disclosure provided herein.

One or more frameworks provided by ADFs 124 may be embodied as OracleADF in one example. Accordingly, a framework in ADFs 124 can be based onan MVC design pattern. An MVC application is separated into: 1) a modellayer that handles interaction with data-sources and runs the businesslogic, 2) a view layer that handles the application UI, and 3) acontroller that manages the application flow and acts as the interfacebetween the Model and the View layers. Separating applications intothese three layers simplifies maintenance and reuse of components acrossapplications. The independence of each layer from the others results ina loosely coupled, SOA.

In various embodiments, ADFs 124 provide tools and resources allowingdevelopers to create an application in the form of multiple layers, eachlayer containing code modules/files implementing desired logic accordingto pre-defined specification. Thus, in one embodiment, ADFS 124 enablesthe application to be developed as four layers: a view layer containingcode modules/files that provide the UI of the application, a controllerlayer containing code modules that control the flow of the application,a model layer containing data/code modules that provide an abstractionlayer for the underlying data, and a business services layer containingcode modules that provide access to data from various sources andhandles business logic.

In certain embodiments, ADFs 124 let developers choose the technologythey prefer to use when implementing each of the layers. EnterpriseJavaBean (“EJB”), Web Services, JavaBeans, JPA/EclipseLink/TopLinkobjects, and many others can all be used as Business Services for ADFs124. View layers can include Web based interfaces implemented with JavaServer Faces (“JSF”), Desktop Swing applications and Microsoft Officefront ends, as well as interfaces for mobile devices.

In one aspect, the view layer represents the UI of the application beingdeveloped. The view layer can include desktop, mobile, and browser-basedviews, each of which provides all or a portion of the UI and isaccessible in a variety of manners corresponding to view type. Forexample, Web pages may be sent by the application in response toreceiving client requests containing corresponding URLs. The Web pagesmay then be displayed by a browser on a display unit (not shown)associated with a requesting client system, thereby enabling users ofthe requesting client system to interact with the enterpriseapplication. ADFs 124 support multi-channel access to business servicesallowing reuse of business services and access from a Web client, aclient-server swing desktop-based application, Microsoft Excelspreadsheets, mobile devices such as a smart-phone, or the like.

The code files/modules forming the view layer (such as Web pages) may beimplemented using one or more of hypertext markup language (“HTML”),Java server pages (“JSP”), and JSF. Alternatively, the UI may beimplemented using Java components such as Swing, and/or XML. As furthernoted, the UI may leverage a user's experience and familiarity withdesktop applications, such as Word and Excel by Microsoft.

As noted above, the relevant user-developed code/data modules areprovided in each of the layers. However, each layer typically containsother pre-defined code/data modules provided by ADFs 124. Some of thepre-defined modules may be used during development, for example, astemplates for developing the Web pages, for including desiredfunctionality in the developed code etc. Other pre-defined modules (suchas a URL rewriting module) may be deployed along with the developedapplication and may provide additional functionalities (mapping ofrequested URLs to internal names) to the user during execution of theenterprise application.

A controller layer contains code modules/files that control the flow ofthe application. Each controller object contains software instructionsand/or data implemented according to a desired manner of presentinginformation in the view layer. The desired manner may include thespecific Web pages to be displayed when links in another Web page areclicked/selected by the user, the page to be displayed when errors occurduring execution, indicating the specific data to be stored/retrieved,etc.

In one aspect, the controller layer manages the application's flow andhandles user input. For example, when a Search button is clicked on apage, the controller determines what action to perform (do a search) andwhere to navigate to (the results page). There are two controlleroptions for Web-based applications in JDeveloper: the standard JSFcontroller or the ADF Controller that extends the JSF controllerfunctionality. Whichever controller is used, application flow istypically designed by laying out pages and navigation rules on adiagram. An application's flow can be broken into smaller, reusable taskflows; include non-visual components such as method calls and decisionpoints in a flow; and create “page fragment” flows that run inside aregion of a single containing page.

The code modules/files forming the controller layer are oftenimplemented as Java servlets receiving the client requests and sendingdesired Web pages as corresponding responses. Controller objects mayalso be implemented, for example, as Apache Jakarta Struts controllersor according to the JSF standard.

A model layer contains data/code modules that connect various businessservices to the objects that use them in the other layers, such as tothe controller objects discussed above or directly to desktopapplications. Each abstract data object of the model layer provides acorresponding interface that can be used to access any type of businessservice executing in an underlying business service layer. The dataobjects may abstract the business service implementation details of aservice from a client and/or expose data control methods/attributes toview components, thus providing a separation of the view and datalayers.

In one aspect, the model layer consists of two components, data controlsand data bindings, which utilize metadata files to define the interface.Data controls abstract the business service implementation details fromclients. Data bindings expose data control methods and attributes to UIcomponents, providing a clean separation of the view and model. Due tothe metadata architecture of the model layer, developers get the samedevelopment experience when binding any type of Business Service layerimplementation to the View and Controller layers.

In certain embodiments, ADFs 124 emphasize the use of the declarativeprogramming paradigm throughout the development process to allow usersto focus on the logic of application creation without having to get intoimplementation details. At a high level, the development process for aFusion Web application usually involves creating an applicationworkspace. Using a wizard, libraries and configuration needed fortechnologies selected by a developer are automatically added and anapplication is structured into projects with packages and directories.

By modeling database objects, an online database or offline replica ofany database can be created, definitions edited, and schemas updated.Using a unified modeling language (“UML”) modeler, use cases can then becreated for the application. Application control and navigation can alsobe designed. Diagrammers can be used to visually determine the flow ofapplication control and navigation. Then, an underlying XML filedescribing the flow can be automatically created. A resource library canbe used to allow a developer to view and use imported libraries bysimply dragging and dropping them into the application. From databasetables, entity objects can be created using wizards or dialogs. Fromthose entity objects, view objects are created to be used by pages inthe application. Validation rules and other types of business logic canbe implemented.

In this example, a business services layer manages interaction with adata persistence layer. It provides such services as data persistence,object/relational mapping, transaction management, and business logicexecution. The business services layer can be implemented in any of thefollowing options: as simple Java classes, EJB, Web services, JPAobjects, and Oracle ADF Business Components. In addition, data can beconsumed directly from files (XML or CSV) as well as REST. Thus, eachbusiness service manages interaction with a corresponding datapersistence layer, and also provides such services as object/relationalmapping, transaction management, business logic execution, etc. Thebusiness services layer may be implemented using one or more of simpleJava classes, Enterprise Java Beans, Web services, etc.

Business components represent a business service implemented using, forexample, “Oracle ADF Business Components” from Oracle Corp., to provideinteraction with databases, Web services, legacy systems, applicationservers, and the like. In one embodiment, business components of thebusiness services layer contain a mixture of application modules,view/query objects, and entity objects, which cooperate to provide thebusiness service implementation. An application module can be atransactional component/code module that UI clients communicate with forworking with application/transaction data. The application module mayprovide an updatable data model and also procedures/functions (commonlyreferred to as service methods) related to user transactions.

An entity object may represent a corresponding row in a database tableand simplify the manipulation (update, deletion, etc.) of the datastored in the corresponding row. An entity object often encapsulatesbusiness logic for the corresponding row to ensure that the desiredbusiness rules are consistently enforced. An entity object may also beassociated with other entity objects to reflect relationships existingbetween rows stored in the underlying database.

FIG. 2 shows a block diagram of a computing environment 200 forfacilitating communication between a mobile computing device andenterprise computer systems according to some embodiments of the presentinvention. For purposes of illustration, various examples are providedherein to describe techniques for enabling a mobile computing device(e.g., computing device 202) to communicate with one or more enterprisecomputer systems, such as a cloud enterprise computer system 240 (e.g.,“serviceprovider.com”) and an on-premises enterprise computer system250. Such communications may be to exchange or transfer enterprise data,request services provided by an enterprise computer system, communicatemessages, or combinations thereof.

Messages may include service invocation messages, result messages,request messages, other messages communicated internally, other messagescommunicated between a computing device and an enterprise computersystem, or combinations thereof. A message may include a message type(e.g., a type value from a set of shared type constants), a correlationid (e.g., an id used to correlate this message with one or more othermessages), priority information to support for priority based messagequeues, timeout, sensitivity indicator to support message dataisolation, message source (e.g., a uniform resource identifier of asender), a message destination (e.g., a uniform resource identifier thatuniquely identifies the destination, a request context (e.g., requestinformation from dispatcher), and/or a message payload. The payload mayhave different attributes depending upon the type of message that isbeing sent, such as parameter data and result data.

Enterprise data as described herein may include data received from anenterprise computer system, data sent to an enterprise computer system,data processed by an enterprise computer system, or combinationsthereof. The enterprise data may be distinguishable from data forconsumer applications and/or services. In some embodiments, for example,enterprise data may change based on application or use of the enterprisedata, whereas data for consumer applications (e.g., consumer data) mayremain static through use. In certain embodiments, enterprise data mayinclude or be associated with rules that indicate criteria for storing,using, and/or managing the enterprise data. For example, enterprise datamay be associated with policy information that indicates one or morepolicies for storing, using, and/or managing the enterprise data. Incertain embodiments, policy information may be included in enterprisedata. In certain embodiments, enterprise data may include dataprocessed, stored, used, or communicated by an application or a serviceexecuting in an enterprise computer system. For example, enterprise datamay include business data (e.g., business objects) such as JSONformatted data from enterprise applications, structured data (e.g., keyvalue pairs), unstructured data (e.g., internal data processed or usedby an application, data in JSON format, social posts, conversationstreams, activity feeds, etc.), binary large objects (“BLOBs”),documents, system folders (e.g., application related folders in asandbox environment), data using REST techniques (referred to herein as“RESTful data”) (e.g., synchronization data made available by RESTendpoints), system data, configuration data, synchronization data, orcombinations thereof. In some embodiments, enterprise data may includeREST-formatted enterprise data. REST-formatted enterprise data mayinclude RESTful data. REST-formatted data may include data formattedaccording to REST techniques implemented by an enterprise computersystem. Configuration or synchronization data may include data used forsynchronization of enterprise data, such as versions, history,integration data, etc. Documents in enterprise data may include XMLfiles, visual assets, configuration files, media assets, etc. A BLOB mayinclude a collection of binary data stored as a single entity in adatabase management system, such as an image, multimedia object, orexecutable code, or as otherwise known in the art.

An enterprise computer system may include various computing systems thatare configured to operate for an entity or an enterprise. For example,an enterprise computer system may include one or more computer systems,such as an enterprise server computer (e.g., a back-end servercomputer), to handle requests for services. An enterprise computersystem may include applications and/or services, which can processand/or operate using enterprise data. For example, enterprise computersystem 250 may provide one or more services and/or applications formanaging or operating an enterprise. Services may include, withoutrestriction, customer relationship management (“CRM”), human capitalmanagement (“HCM”), human resource (“HR”) management, supply chainmanagement, enterprise communication, email communication, businessservices, other enterprise management services or applications, orcombinations thereof. Enterprise computer system 250 may include one ormore computer systems dedicated to providing one or more services. Insome embodiments, each different computer system providing a service maybe located on-premise of an enterprise or may be located remotely froman enterprise. In some embodiments, multiple different computer systemssupporting different services may be situated in a single geographicallocation, such as on-premises of an enterprise. In the example shown inFIG. 2, on-premises enterprise computer system 250 may include an HRsystem 254 and a CRM system 256, both of which may be locatedon-premises of an enterprise. In some embodiments, enterprise computersystem 250 may include or implement an agent system 252 to facilitate orhandle communication between cloud computer system 210 and one or moreenterprise systems 254, 256. Enterprise computer systems, such as cloudenterprise computer system 240 and on-premises enterprise computersystem 250 are described below in further detail.

The computer environment 200 may include MCS 212 implemented to operateas a secure intermediary computing environment that may facilitatecommunication between the computing device 202 and one or moreenterprise computer systems because computing device 202 may not beconfigured to communicate with such enterprise computer systems. Forexample, some enterprise computer systems may be supported by legacy orback-end computer systems. Such systems may be configured to operateusing different communication and/or security protocols. The protocolssupported by such enterprise computer systems may be different fromthose supported by mobile computing devices. MCS 212 may supportcommunication with different types of mobile computing devices. As such,MCS 212 may implement techniques to facilitate communication betweenenterprise computer systems and mobile computing devices to enable themto communicate with each other despite their incompatibilities incommunication, such as differences between formats or communicationprotocols. For example, MCS 212 may translate communication protocolsbetween mobile computing devices and enterprise computer systems.

Cloud computer system 210 may support MCS 212. Cloud computer system 210may be implemented using hardware, software, firmware, or combinationsthereof. For example, cloud computer system 210 may include one or morecomputing devices, such as a server computer. Cloud computer system 210may include one or more memory storage devices and one or moreprocessors. A memory storage device can be accessible to theprocessor(s) and can include instructions stored thereon which, whenexecuted by the processor(s), cause the processor(s) to implement one ormore operations disclosed herein. In some embodiments, the memorystorage devices may operate as local storage (e.g., cache). Cloudcomputer system 210 may include different kinds of operating systems. Amemory storage device may be accessible to the processor(s) and mayinclude instructions stored thereon which, when executed by theprocessor(s), cause the processor(s) to implement one or moreoperations, methods, or processes disclosed herein. The memory storagemay operate as local storage. Local storage may be implemented using anytype of persistent storage device, such as a memory storage device orother computer readable storage medium. In some embodiments, localstorage may include or implement one or more databases (e.g., a documentdatabase, a relational database, or other type of database), one or morefile stores, one or more file systems, or combinations thereof. Thelocal storage may store enterprise data.

In certain embodiments, cloud computer system 210 may include one ormore data stores, such as a metadata repository 224, diagnostics store226, and an analytics store 228. The data stores 224, 226, 228 may beaccessible by any component in cloud computer system 210.

Metadata repository 224 may store all the metadata associated with MCS212. This information may be composed of both run-time and design-timedata, each having their own requirements on availability andperformance. A tenant or subscriber of MCS 212 may have any number ofapplications. Each application may be versioned and may have anassociated zero or more versioned resource APIs and zero or moreversioned services implementations those resource API contracts. Theseentities are what the run-time uses to map virtual requests (mAPIs) tothe concrete service implementation (service). This mapping provides amobile developer with the luxury of not having to know the actualimplementation service when she designs and builds her application. Aswell as not requiring her to have to republish a new application onevery service bug fix. Metadata repository 224 may store one or morecallable interfaces, which may be invoked by a computing device (e.g.,computing device 202). The callable interfaces may be customizable by auser (e.g., a developer) of an application to facilitate communicationwith MCS 212. Metadata repository 224 may store metadata correspondingto one or more configurations of a callable interface. Metadatarepository 224 may be configured to store metadata for implementing acallable interface. The callable interface may be implemented totranslate between a one format, protocol, or architectural style forcommunication and another format, protocol, or architectural style forcommunication. Metadata repository 224 may be modifiable by anauthenticated user via the external network.

Diagnostics store 226 may store diagnostics information about processingoccurring in MCS 212. Diagnostics store 226 may store messagescommunicated via MCS 212 and log information. Analytics store 228 maystore logging and analytics data captured during processing in thesystem.

On behalf of MCS 212, cloud computer system 210 may utilize itscomputing resources to enable execution of custom code 216 (e.g.,operations, applications, methods, functions, routines, or the like).Computing resources may be allocated for use with respect to aparticular user associated as a subscriber or tenant to MCS 212.Resources may be allocated with respect to a user, a device, anapplication, or other criterion related to a subscriber. MCS 212 may bescaled in or out, depending on the demand of mobile computing devicesseeking to communicate with enterprise computer systems. MCS 212 can beconfigured such that it is elastic to handle surges and temporaryperiods of higher than normal traffic between mobile computing devicesand enterprise computer systems. In some embodiments, MCS 212 mayinclude elements that support scalability such that components may beadded or replaced to satisfy demand in communication.

Computing device 202 may communicate (e.g., send a request message) withMCS 212 to request service provided by an enterprise computer system.Computing device 202 (e.g., a mobile computing device) may beimplemented using hardware, firmware, software, or combinations thereof.Computing device 202 may communicate with enterprise computer systems240, 250 via MCS 212. Computing device 202 may include or may beimplemented as an endpoint device, a PDA, a tablet computer, a laptopcomputer, a mobile computing device, a desktop computer, a wearablecomputer, a pager, etc. Computing device 202 may include one or morememory storage devices and one or more processors. Computing device 202may include different kinds of operating systems. A memory storagedevice may be accessible to the processor(s) and may includeinstructions stored thereon which, when executed by the processor(s),cause the processor(s) to implement one or more operations, methods, orprocesses disclosed herein. The memory storage may operate as localstorage. Local storage may be implemented using any type of persistentstorage device, such as a memory storage device or other computerreadable storage medium. In some embodiments, local storage may includeor implement one or more databases (e.g., a document database, arelational database, or other type of database), one or more filestores, one or more file systems, or combinations thereof. The localstorage may store enterprise data.

In various embodiments, computing device 202 may be configured toexecute and operate one or more applications such as a web browser, aclient application, a proprietary client application, or the like. Theapplications can include specific applications configured for enterprisedata and/or services provided by an enterprise computer system. Clientapplications may be accessible or operated via one or more network(s).Applications may include a graphical UI (“GUI”) for operating theapplication.

Computing device 202 may communicate with MCS 212 via one or morecommunication networks using wireless communication. Examples ofcommunication networks may include a mobile network, a wireless network,a cellular network, a LAN, a wide area network (“WAN”), other wirelesscommunication networks, or combinations thereof. In certain embodiments,computing device 202 may establish a communication connection 214 withMCS 212 using a custom communication protocol (e.g., a custom protocol).Connection 214 may be established with MCS 212 through cloud computersystem 210. The custom protocol may be an HTTP-based protocol. Byutilizing a custom communication protocol, computing device 202 mayoperate on any computing device platform to communicate with cloudcomputer system 210.

Computing device 202 may communicate with cloud computer system 210through one or more callable interfaces, e.g., APIs. A callableinterface may be implemented on computing device 202. The callableinterface may be implemented for custom applications that enable thoseapplications to communicate with MCS 212. In some embodiments, acallable interface may be developed for MCS 212. The callable interfacemay enable applications to communicate with MCS 212 without having toadapt to differences in protocols (e.g., communication or developmentprotocols) and/or architectural styles or formats.

MCS 212 may be protected by one or more firewalls 204, 230 to provide asecure environment to process requests and execute custom code 216.Communication between computing device 202 and MCS 212 may be separatedby an external communication firewall 204. Firewall 204 may be connectedwith cloud computer system 210 to facilitate secure access to MCS 212.Firewall 204 may permit communication of messages between cloud computersystem 210 and computing devices (e.g., computing device 202). Suchmessages (e.g., HTTP messages or REST messages) may conform to acommunication protocol (e.g., HTTP or REST), which may be supported by acallable interface. In another example, a message between cloud computersystem 210 and computing device 202 may conform to a communicationprotocol such as SPDY. MCS 212 may manage firewall 230 to securecommunication between cloud computer system 210 and enterprise computersystems 240, 250. Firewall 230 may permit communication of messagesbetween cloud computer system 210 and computing devices (e.g., computingdevice 202). Such messages (e.g., SPDY messages, HTTP messages or RESTmessages) may conform to a communication protocol (e.g., SPDY, HTTP, orREST). Communication between computing device 202 and enterprisecomputer systems 240, 250 may be two-way via MCS 212.

Because communication with computing device 202 and enterprise computersystems 240, 250 may occur via an unsecure, public network, firewalls204, 230 provide an added layer of protection for communications to andfrom MCS 212. Firewalls 204, 230 may enable MCS 212 to distinguish itsinternal network from an external network connecting computing device202 and enterprise computer systems 240, 250. In some embodiments,firewalls 204, 230, although shown as two distinct firewalls, may beimplemented as a single firewall that encapsulates MCS 212.

Cloud computer system 210 may further operate as an intermediarycomputing environment by communicating with enterprise computer systems,some of which may have different communication protocols. Suchcommunication protocols may be custom or specific to an application orservice in communication with cloud computer system 210. Further, cloudcomputer system 210 may communicate with an enterprise computer systemto provide enterprise services and/or to exchange enterprise dataaccording to a format supported by the enterprise computer system. Cloudcomputer system 210 may maintain local storage (e.g., local cache) ofenterprise data and may use the local storage to manage synchronizationof the enterprise data between mobile computing devices and enterprisecomputer systems 240, 250.

Computing device 202 may communicate (e.g., send a request message) withMCS 212 to request service provided by an enterprise computer system.Requests that are received through firewall 204 may be processed firstby security service 232. Security service 232 may manage securityauthentication for a user associated with a request. Thus, a cloudcomputer system may provide technical advantages that include providingsecurity mechanisms described herein which may protect the integrity ofcustomer communications and enterprise data. Technical advantages ofcloud computer system may include preventing or reducing compromisedcommunications and/or data from being compromised, authentication mayoccur initially, restricting access to only those who have the requiredcredentials. Technical advantages of cloud computer system may includethe services and service invocation flow being structured such that asrequests come in they may only be able to access services for which theyare authorized. By decoupling authorization from the rest of the systemprocessing, another technical advantage may include the task ofauthorizing “what can be done by whom” being delegated to a dedicatedprovisioned security subsystem (e.g., an identity management system)that may be expanded to support whatever additional custom securitymeasures are required by a specific corporate customer. In someembodiments, security authentication may be determined for a request, asession, a user, a device, other criterion related to the user, orcombinations thereof. Security authentication may be performed for eachrequest that is received. In some embodiments, security service 232 maydetermine authentication based on a previous verification of a request.Security authentication may be determined for a user or a device suchthat requests to different enterprise computer systems 240, 250 may beauthenticated based on a single verification of security.

Further technical advantages of the invention may include a cloudcomputer system enabling a computing device to communicate with variousenterprise computer systems, some of which may be implementeddifferently. For example, a computing device 202, cloud computer system210, and enterprise computer system 250 may be located at differentgeographical locations, physically separated from each other. Therefore,computing device 202 can communicate with enterprise computer system 250regardless of their location. Technical advantages may include a cloudcomputer system enabling a computing device to communicate requests forservices to enterprise computer systems, which may support one or moredistinct security protocols. In some cases, an enterprise computersystem may be supported by a back-end system that is not easilyadaptable to a different security protocol. In some cases, it may bedesirable for developers of applications to be able to implement anapplication to be able to request services without knowledge of suchsecurity protocols. It may be equally desirable for a user (e.g., anadministrator or an architect) of an enterprise computer system to beable to receive requests without accommodating for different types ofapplications, security protocols, and standards. Technical advantagesmay enable such desires to be met by implementation of a cloud computersystem, as described herein, which can handle security authentication,such that requests can meet the security measures of differententerprise computer systems that are being requested.

In some embodiments, security service 232 may determine a securityprotocol for a requested enterprise computer system and accordinglygenerate a security token according to such security protocol. Thesecurity token may be passed along with a request to an enterprisecomputer system to enable that enterprise computer system to verifyauthentication based on the generated security token. Enterprisecomputer systems may support different security protocols. A securityprotocol may be a standard by which security is determined. Security maybe verified based on a security token that is generated by securityservice 232. Security service 232 may determine a security protocol foran enterprise computer system identified for a request. In someembodiments, an enterprise computer system 250 may have an agent system252, which may be configured or implemented according to a custom orspecific security protocol supported by MCS 212. As such, MCS 212 maygenerate a security token according to such custom security protocol.

Cloud computer system 210 may include, implement, and/or communicatewith one or more load balancer systems 206, 208. Upon determiningsecurity authentication, cloud computer system 210 may request any oneof load balancer systems 206, 208 to examine a request that it receivesand to detect which service the request is directed to. MCS 212 may beconfigured with load balancers 206, 208 and updated with resources thatget started up, so that when a request comes in, load balancers 206, 208can balance a requested load across the different resources.

Cloud computer system 210 may include a dispatcher 218 that may handlerequests and dispatch them to the appropriate service. A request may berouted to an appropriate service upon dispatch. In some embodiments, aservice itself may route an internal request to another internal servicein MCS 212 or in an enterprise computer system. In some embodiments,dispatcher 218 may resolve a request to determine its destination basedon a location (e.g., an address) of a destination identified in a URIand/or URL of the request. Dispatcher 218 may parse a request and itsheader to extract one or more of the following information: tenantidentifier, service identifier, application name, application version,request resource, operation and parameters, etc. Dispatcher 218 can usethe parsed information to perform a lookup in metadata repository 224.Dispatcher 218 may retrieve a corresponding application metadata.Dispatcher 218 may determine the target service based on the requestedresource and the mappings in the metadata. While initially a very basicmapping, the metadata can be enhanced to provide for more sophisticated,rules-based dispatching. Dispatcher 218 may perform anydispatcher-specific logging, metrics gathering, etc. Dispatcher 218 maythen perform initial authorization according to the applicationmetadata. Dispatcher 218 may format the inbound request and any othernecessary information and place the message on routing bus 220 forfurther processing. Dispatcher 218 may place a request on a queue andawait the corresponding response. Dispatcher 218 may process responsesreceived from routing bus 220 and return a response to computing device202.

In addition to handling the dispatching for external requests,dispatcher 218 may also play a role in dispatching internal requests.Such internal requests can come in the form of composite services orcustom code invocations to services. In both cases, the caller could usea logical service name as defined within the application. Dispatcher 218may use the current execution context to determine the application anduse that logical name to determine the appropriate service to invoke.

Cloud computer system 210 may include a routing bus 220 to managedeliver of messages to destinations registered with routing bus 220.Routing bus 220 may operate as a central system for managingcommunications in cloud service 212. Data communicated through routingbus 220 may be processed to capture and store the data. Routing bus 220may provide a framework so that additional centralized services(additional authorization, debugging, etc.) can be plugged in easily asnecessary. Data captured by routing bus 220 may be stored in diagnosticsstore 226 and/or analytics store 228.

Routing bus 220 may route messages to one or more destinations. In someembodiments, a message may include a request to execute custom code 216.In such embodiments, routing bus 220 may request 234 custom code 216 tobe invoked. In some embodiments, routing bus 220 may pass on a requestto a destination enterprise computer system identified by information ina request. Routing bus 220 may request 236 an adaptor interface 222 toperform translations, if necessary, to pass a request to an enterprisecomputer system, e.g., enterprise computer system 240 or enterprisecomputer system 250.

In certain embodiments, cloud computer system 210 may include orimplement adaptor interface 222 to translate or convert a message to aprotocol supported by a receiving enterprise computer system. Adaptorinterface 222 may establish separate communication connections with eachof enterprise computer systems 240, 250. Cloud computer system 210 maybe configured to communicate with enterprise computer systems 240, 250via one or more networks (not shown). Examples of communication networksmay include the Internet, a mobile network, a public network, a wirelessnetwork, a cellular network, a LAN, a WAN, other communication networks,or combinations thereof. In certain embodiments, communicationconnections may be high-speed communication connections facilitatedusing high-speed communication trunks. Communication with an enterprisecomputer system 240, 250 may pass through firewall 230 which ensuresthat communication with an external network is secure to preventunauthorized access to MCS 212 via such communications.

In some embodiments, cloud computer system 210 may facilitatenotifications to a user of computing device 202. Cloud computer system210 may include an alert management service that supports statefulinteraction with a user, for example to deliver an alert based on userpreferences through one or more channels, wait for a response, and takeaction based on the response. Responses to an alert sent on one channelmay be received through another channel, which the service needs to beable to handle. The platform may come with built-in state models forpopular interaction patterns and be extensible with new state models.Some alert channels may include known communication resources, eitherone-way or two-way. Examples include SMS, Twitter®, push notifications,and Google Cloud Messaging®.

In some embodiments, cloud computer system 210 may enable computingdevice to access and/or request one or more services, such as an objectstore service, database service, access web services, social services,resource services, or combinations thereof.

Cloud computer system 210 may provide an object store service that mayprovide a storage facility for BLOBs. The basic unit of storage can betext, with read and write operations. A basic query facility for JSONobjects may also be offered.

Cloud computer system 210 may provide a database service to allow forconnectivity to hosted databases for performing queries or writes.Required parameterization may require the full connection string for thedatabase, the SQL string or stored procedure to execute, any parametersand possibly credentials. The necessary information can be provided atrun time or be pre-configured in the application metadata.

Cloud computer system 210 may provide access to web services such asSOAP web services. Cloud computer system 210 may provide access to RESTservices, such as connectivity to arbitrary REST resources.

Cloud computer system 210 may provide access to social services that mayprovide basic integration with many of the popular social sites such asFacebook®, Twitter®, etc. These services may allow for third partyauthentication using the user's credentials from those sites as well asaccess to their services. Examples include sending a tweet or updatingyour status.

Cloud computer system 210 may provide a public cloud service to enable auser to simplify and optimize communication. For example, a servicedeveloper may use the generic web service of MCS 212 to talk to aresource hosted using cloud computer system's 210 cloud service.

A cloud computer system, such as one described herein, may enable mobilecomputing devices to communicate with enterprise computer system despitedifferences in computing resources. A cloud computer system may beequipped with more resources and a faster, more reliable connection toenterprise computer systems to communicate frequently to receiveenterprise data. The cloud computer system may manage and coordinaterequests for services from enterprise computer systems. By translatingrequests to a protocol supported by a recipient of a message, the cloudcomputer system reduces a burden on developers to configure applicationsfor communication with different types of back-end computer systems.Enterprises are able to maintain their back-end systems without havingto accommodate advances or changes in communication protocols supportedfor mobile devices. Different enterprise computer systems may supportdifferent security protocols based on a type of requests processed andservices provided. By managing security authentication in a centralizedmanner for access to different enterprise computer systems, enterprisecomputer systems do not need to adapt to differences in securityprotocols. By authenticating a user of the cloud computer system,processing requests can become more efficient as authentication may notbe performed in every instance.

In some embodiments, an application may be deployed under a mobileapplication framework (“MAF”) that provides built in security to controlaccess to the application and ensure encryption of sensitive data, suchas Oracle MAF from Oracle Corp. MAF is a hybrid mobile architecture thatuses HTML5 and Cascading Style Sheets (“CSS”) (to render the UI in theweb view), Java (for the application business logic), and Apache Cordova(to access device features such as GPS activities and e-mail). BecauseMAF uses these cross-platform technologies, the same application can bebuilt for both Android and iOS devices without having to use anyplatform-specific tools. After an application is deployed to a device,it behaves as applications created using such platform-specific tools asObjective C or the Android SDK. Further, MAF allows for building thesame application for smartphones or for tablets, thereby allowing reuseof business logic in the same application and targeting various types ofdevices, screen sizes, and capabilities.

FIG. 3 illustrates an example mobile application springboard 300 thatincludes a MAF application 302 called “WorkBetter” that is deployed as a“heavy” application (e.g., a mobile application that sits in a mobiledevice in the same manner as a normal iPhone “app” obtained from the Appstore). A MAF application may include one or more embedded applicationsadded as application features. Such added application features arerepresented as icons within the main application's springboard ornavigation bar. Application features are essentially the building blocksof such mobile application. Each application feature that is integratedinto a MAF application performs a specific set of tasks. Applicationfeatures can be grouped together to complement each other'sfunctionality. For example, an application feature that providescustomer contacts may be paired with one for product inventory. Becauseeach application feature has its own class loader and web view,application features are independent of one another, thus a single MAFapplication can be assembled from application features created byseveral different development teams. Application features can also bereused in other MAF applications. A MAF application itself can be reusedas the base for another application, allowing independent softwarevendors (“ISVs”) to create applications that can be configured byspecific customers.

In addition to hybrid mobile applications that run locally on thedevice, application features may be implemented as any of the followingmobile application types, depending on the requirements of a mobileapplication and available resources:

-   -   For mobile web applications hosted on a server, although the        code can be portable between platforms, access to device        features and local storage can be limited as these applications        are governed by the device's browser.    -   Native applications are authored in either Xcode or through the        Android SDK and are therefore limited in terms of serving both        platforms. Reuse of code is likewise limited.

MAF supports authentication and access control for refined security atthe feature level in an application where a developer can specify anappropriate login server, e.g., a server running “Oracle IdentityManagement” and/or “Oracle WebLogic” with basic authentication, a serversupporting OAuth protocols, etc. At runtime users are presented withlogin screens and appropriate tokens are accessible for further Webservice calls. With MAF, developers can build single UIs that meet theneeds of users with different privileges (e.g., show/hide componentsbased on user role or privilege).

MAF enforces communication encryption using SSL/TLS (HTTP secure(“HTTPS”)), on-device encryption to keep credentials in an encrypted keystore to be used for validation when supporting offline authentication,and SQLite database encryption by using the SQLite encryption extension.Encrypting an SQLite database for an application built with MAF may beperformed via a configuration option when the application is developed.In some embodiments, MAF supports offline and online modes of operationfor an application so a self-contained application can run on a mobiledevice in connected and disconnected modes. For data access/storage,such application may leverage a local encrypted SQLite database. Theapplication may be built such that initial access to data is performedfrom remote servers through Web services, and the data is then stored inthe local SQLite database for offline access. The data can be replicatedand synchronized to the server when connectivity is available again. MAFalso supports local storage of user authentication credentials to enableoffline authentication/authorization to secured applications.

FIGS. 3A and 3B illustrate an HR mobile application UI 304 in accordancewith an embodiment of the present invention. UI 304 may be provided uponopening an icon on a springboard such as mobile application springboard300 of FIG. 3. In FIG. 3A, UI 304 includes various HR relatedinformation about an employee, such as picture, title, contactinformation, social networking information, performance/ratinginformation, compensation information, manager, skills, location, etc.FIG. 3B indicates various sources where the information in UI 304 may beobtained from, such as services located on premise or in the cloud. Forexample, basic employee information may be obtained from on premise coreHR services 306 such as PeopleSoft, Systems, Applications & Products(“SAP”), etc., while location information is obtained from a map service308 such as Google. Similarly, performance information may be obtainedfrom a talent management cloud service 310 such as TALEO, and socialnetworking information 312 (e.g., Twitter, Facebook, LinkedIn, etc.) maybe obtained from the web. In one embodiment, the information from thesevarious sources is channeled through MCS 212 (see FIG. 2) before beingsent down to the application on the mobile device 202 (see FIG. 2).

FIG. 4 is a block diagram of a MAF runtime architecture 400 according toan embodiment. Runtime architecture 400 includes a “thin” device nativecontainer 402 deployed to a mobile device 404. Runtime architecture 400represents the MVC development approach which separates the presentationfrom the model layer and the controller logic. Device native container402 allows a MAF application to function as a native application ondifferent platforms (e.g., iOS, Android, etc.) by interacting with alocal SQLite database 406 (via SQLite 408), mobile device services 426(via Cordova APIs of Apache Cordova 410), and server-side resources 412such as a Configuration Server 444, Server-Generated HTML 430, PushServices 448, and Web Services 440.

Device Services 426 are services and features that are native to device404 such as camera, GPS, e-mail, etc. Configuration Server 444 is aserver based on Web Distributed Authoring and Versioning (“WebDav”) andhosting configuration files used by the application configurationservices. WebDav is defined in, e.g., Internet Engineering Task Force(“IETF”) Request for Comments (“RFC”) 4918. Configuration Server 444 isdelivered as a reference implementation. Any common WebDav serviceshosted on a Java 2 Platform, Enterprise Edition (“J2EE”) server can beused for this purpose. Server-Generated HTML 430 includes Web contenthosted on remote servers and used for browser-based applicationfeatures. Push Services 448 may include, for example, Apple PushNotification Services (“APNs”) and Google Cloud Messaging (“GCM”) pushservices that are notification providers that send notification eventsto MAF applications. Web Services 440 are, for example, remotely hostedSOAP-based web services.

Device native container 402 includes Web View 416 that uses a mobiledevice's web engine to display and process web-based content. In a MAFapplication, Web View 416 delivers the UI by rendering the applicationmarkup as HTML 5. The UI may be created for a mobile application featureby implementing any of the following content types: MAF ApplicationMobile XML (“AMX”) Views 420, Controller 422, local HTML 424, or serverHTML 428, where MAF AMX Views 420, Controller 422, and local HTML 424provide HTML5 and JavaScript presentation 418. Application featuresimplemented from various content types can coexist within the samemobile application and can also interact with one another.

Applications whose contents are implemented as MAF AMX views 420 resideon device 404 and provide the most authentic device-native userexperience, similar to an application authored in the language specificto the device's platform. MAF provides a set of code editors that enablea user to declaratively create a UI from components that are tailored tothe form factors of mobile devices. These components can be used tocreate the page layout (e.g., list view) as well as input components(e.g., input fields). When a user develops MAF AMX views 420, they canleverage data controls which enable the user to declaratively createdata-bound UI components and access a Web service and the services of amobile device (e.g., camera, GPS, or e-mail). At runtime, a JavaScriptengine in Web View 416 renders MAF AMX view definitions into HTML5 andJavaScript.

For applications whose contents are implemented as Controller 422,Controller 422 governs the flow between pages in the mobile application.Controller 422 enables a user to break an application's flow intosmaller reusable task flows and include non-visual components such asmethod calls and decision points. In the embodiment of FIG. 4,Controller 422 is included in MAF AMX Views 420 and is called by MAF AMXViews 420 to, e.g., transition a page and/or activate actions. However,in alternative embodiments, Controller 422 may be implemented as a peerof MAF AMX Views 420.

For applications whose contents are implemented as local HTML 424, HTMLpages run on the device as part of the MAF application. Local HTML filescan access device-native features and services through Apache Cordova410 and JavaScript APIs.

For applications whose contents are implemented as server HTML 428, theUI is delivered from server-generated Web pages (Server-Generated HTML430) that can open within the application feature's Web View 416. Withinthe context of MAF, this content type is referred to as remote URL. Theresources for these browser-based applications do not reside on thedevice 404. Instead, the UI, page flow logic, and business logic aredelivered from a remote server.

When one of these remotely hosted Web applications is allowed to openwithin Web View 416, it can use Cordova JavaScript APIs to access anydesignated device-native feature or service such as the camera or GPScapabilities. When implementing an application using the remote URLcontent, a user can leverage an existing browser-based application thathas been optimized for mobile use, or use one that has been writtenspecifically for a specific type of mobile device. For applications thatcan run within the browsers on either desktops or tablets, the user canimplement the remote URL content using applications created through richclient-based components such as those provided by “Oracle ADF Faces”from Oracle Corp. For applications specifically targeted to mobilephones, the remote URL content can be delivered from Web pages createdusing MAF. Not only can applications authored with MAF render on avariety of smartphones, but they can gracefully degrade to the reducedcapabilities available on feature phones through UIs constructed withApache Trinidad JSF components and dynamically selected style sheets.Because the content is served remotely, the application is availableonly as long as the server connection remains active.

Device native container 402 further includes Apache Cordova 410 thatprovides JavaScript APIs that integrate the device's native features andservices into a mobile application. Although a user can access theseAPIs programmatically from Java code (or using JavaScript whenimplementing a MAF mobile application as local HTML 424), the user canadd device integration declaratively when creating MAF AMX pages becauseMAF packages these APIs as data controls.

Device native container 402 further includes a Java Virtual Machine(“JVM”) 432. Java provides a Java runtime environment for a MAFapplication. JVM 432 is implemented in device-native code, and isembedded (or compiled) into each instance of the MAF application as partof the native application binary. JVM 432 is based on the Java Platform,Micro Edition (“Java ME”) Connected Device Configuration (“CDC”)specification. In runtime architecture 400, JVM 432 includes businesslogic 434, model 436, and Java database connectivity (“JDBC”) 438. Javaenables business logic 434 in MAF applications. Managed Beans (“MBeans”)are Java classes that can be created to extend the capabilities of MAF,such as providing additional business logic for processing data returnedfrom the server. MBeans are executed by the embedded Java support, andconform to the Java ME CDC specifications. Model 436 includes thebinding layer that connects the business logic components with the UI.In addition, the binding layer provides the execution logic to invokeweb services 440 such as remotely hosted SOAP-based web services. Theseservices are accessed through the Java layer (JVM 432). Applicationfeatures authored in MAF AMX access SOAP-based data services throughdata controls. JDBC 438 is an API that enables the model layer to accessthe data in encrypted SQLite database 406 through Create, Read, Update,and Delete (“CRUD”) operations.

Device native container 402 further includes Application Configuration442 which refers to services that allow application configurations to bedownloaded and refreshed, such as URL endpoints for a web service or aremote URL connection of a configuration server 444. Applicationconfiguration services download the configuration information from aserver-side WebDav-based service.

Device native container 402 further includes module 446 that providesCredential Management, Single Sign-on (“SSO”), and Access Control. MAFhandles user authentication and credential management through the“Oracle Access Management Mobile and Social” (“OAMMS”) identity manager(“IDM”) SDKs. MAF applications perform offline authentication, meaningthat when users log in to the application while connected, MAF maintainsthe username and password locally on device 404, allowing users tocontinue access to the application even if the connection to theauthentication server becomes unavailable. MAF encrypts the locallystored user information as well as the data stored in local SQLitedatabase 406. After authenticating against the login server, a user canaccess all of the application features secured by that connection. MAFalso supports the concept of access control by restricting access toapplication features (or specific functions of application features) byapplying user roles and privileges. For remotely served Web content, MAFuses whitelists to ensure that only the intended URIs can open withinthe application feature's web view 416 (and access the device features).

Device native container 402 also enables push notifications via a PushHandler 414 that communicates with push services 448 included in serverside resources 412 and enables MAF applications to receive events fromnotification servers such as the iOS or Android notification servers.The Java layer (JVM 432) handles the notification processing.

In runtime architecture 400, device native container 402 interacts withencrypted SQLite Database 406 that is an embedded SQLite database thatprotects locally stored data and is called by the model layer using JDBC438. The MAF application generates this lightweight, cross-platformrelational database 406. Because database 406 is encrypted, it securesdata if the device is lost or stolen. Only users who enter the correctuser name and password can access the data in this database.

FIG. 5 is a block diagram of a system 500 for developing mobileapplications in a mobile cloud infrastructure in accordance withembodiments of the present invention. In system 500, a user may use auser device 528 to develop and build applications in a cloudinfrastructure 506 via a Web based tool. In one embodiment, theapplications may be downloaded on a mobile device 526 over the air, thusobviating the need for an App store. The native applications talk tobackends 504 created in MCS 502. In one embodiment, MAF runtimearchitecture 400 of FIG. 4 may be used to deliver an application tomobile device 526. In one embodiment, a declarative syntax of anapplication is deployed on mobile device 526 over the air, and thedeclarative syntax is interpreted on mobile device 526 by MAF runtimearchitecture 400 of FIG. 4.

Cloud infrastructure 506 includes MCS 502 that provides an admin UI 516through which application development may be performed. MCS 502 furtherincludes production environments 512 and testing environments 514 inwhich a mobile application may be developed and tested, respectively.These environments provide production/testing functionality by talkingto corresponding backends 504 via connectors. An application is firstdeveloped in testing environments 514. Once published, the applicationmoves to production environments 512.

In one embodiment, a mobile application is developed by using userdevice 528 to communicate with MCS admin UI 516 (also referred to asportal) through a security layer 524. MCS admin UI 516 includes anapplication development server 518 that can be interfaced via MCS adminUI 516. An application that is developed in MCS admin UI 516 can be runon a browser of user device 528 or on mobile device 526 by communicatingwith production environments 512 and/or testing environments 514. In oneembodiment, when an application is deployed on mobile device 526, mobiledevice 526 communicates with testing environments 514. However, if theapplication is updated on mobile device 526, such updates are performedthrough MCS admin UI 516.

An application that is developed in system 500 may be built as a lightapplication or a heavy application. A heavy application is a fullapplication such as apps that are downloaded from an App store. A lightapplication is an application that is deployed as an added feature to analready deployed full application (i.e., a hosting application) such asan Oracle app. The hosting application acts as a container that holdsthe light applications. Both heavy and light applications can be furthercontainerized by a security container, as described herein withreference to FIG. 7.

FIG. 6 is a block diagram of network components in a system 600 forbuilding mobile applications in accordance with embodiments of thepresent invention. In system 600, a first device 602 interacts with anMCS website (denoted as “https://mcs-tenant-a.cloud.oracle.com” in theexample embodiment of FIG. 6) to initiate build requests, and a seconddevice 604 communicates with the MCS website to perform an over the airinstall of native applications. Generally, the over the air installincludes downloading a file such as a property list file (a “p-list”file with extension “.plist”) that describes the application and thelocation from which to download the corresponding application archivefile (a file with “.ipa” extension and storing the application), andthen downloading the application archive file from that location.

First device 602 and second device 604 interact with the MCS website bycommunicating with an MCS Portal VM 612 of a server 610 through a publicOracle HTTP Server (“OHS”) 606. Public OHS 606 is a public facing HTTPserver that directs traffic to MCS Portal VM 612 located behind afirewall 608. Public OHS 606 implements a WebGate that is a web serverplugin for Oracle Access Manager (“OAM”) to intercept HTTP requests andforward them to the corresponding Access Server for authentication andauthorization. Accordingly, public OHS 606 authenticates the user offirst device 602, passes along user credentials to MCS Portal VM 612,and terminates the SSL connection with first device 602. In the exampleembodiment of FIG. 6, first device 602 and second device 604 accesspublic OHS 606 at “https://mcs-tenant-a.cloud.oracle.com” with port 443used for https.

MCS Portal VM 612 is a standard WebLogic Server (“WLS”) applicationwhose data is backed by a single tenant schema in schema service 614 andits corresponding application development client is written using theOracle Jumpstart Enterprise Toolkit (“JET”) framework. WebLogic Serveris a Java EE application server developed by Oracle Corp. A databaseschema is a container of objects (e.g., tables, views, storedprocedures, etc.) to logically group them.

MCS Portal VM 612 is a single tenant and its security is provided viaOracle Web Services Manager (“OWSM,” described herein with reference toFIG. 7). Accordingly, MCS Portal VM 612 runs WLS in a trusted zone. MCSPortal VM 612 handles requests by first device 602 and has a connectionto a schema service 614. MCS Portal VM 612 is also connected to a buildserver farm 618 via a load balancer 616. In the embodiment of FIG. 6,MCS Portal VM 612 uses open port 80 (or equivalent) for httpcommunication to/from Public OHS 606, to load balancer 616, and fromindividual servers in server farm 618.

Schema service 614 interacts with the MCS Portal VM 612 and storesapplication data, enterprise signing certificates, and provisioningprofiles for the tenant. Load balancer 616 routes farm tasks to serversin server farm 618. The routing may initially be performed in around-robin fashion. In the embodiment of FIG. 6, load balancer 616 is aBIG-IP appliance from F5 Corp. which uses open port 80 (or equivalent)and provides redundancy. Server farm 618 includes a number of servers(e.g., 20 servers) that handle build jobs. It is connected to a filer(not shown) for storing application binaries (e.g., 5TB). In oneembodiment, connections of server farm 618 are handled via a localTomcat instance running locally on a server, and build tools andprocesses are handled by native OSX calls.

Building an Application

In one embodiment, once a user of first device 602 has created anapplication and wishes to produce a native binary, the user initiates abuild POST request at the MCS website (e.g., at“https://mcs-tenant-a.cloud.oracle.com/max/build”) via a UI of firstdevice 602. POST is a request method supported by the HTTP protocol forrequesting a web server to accept and store the data enclosed in thebody of the request message. The payload of the build POST requestincludes the application identifier (“ID”) for the application. PublicOHS 606 receives the request, terminates the SSL, authenticates andauthorizes the user against OAM (assuming the user is logged in), placesthe user identity into HTTP headers of the request, and forwards therequest past firewall 608 to the WLS server of MCS Portal VM 612 (e.g.,the WLS server running at “http://mcs-tenant-a.internal/max/build”).

MCS Portal VM 612 receives the request, authorizes the user forprivileges against the requested application, and sends a query to thetenant schema service 614 for application data, tenant enterprisecertificate, encrypted certificate password, and tenant provisioningprofile. Once schema service 614 returns the requested items, MCS PortalVM 612 creates a new entry in a table of build jobs (stored at schemaservice 614) to record the build attempt and capture the primary key ofthe corresponding new build record. MCS Portal VM 612 also creates a newPOST request against build server farm 618 behind load balancer 616(e.g., at “http://max-mini-farm.internal/build/initiate”), passing inthe corresponding parameters (application data, signing certificate andpassword, and provisioning profile) into the body of the request as wellas a callback URL for job completion, where the callback URL encodes theprimary key of the corresponding build record in the table of buildjobs. The following functionality provides an example of a build POSTrequest payload that includes the corresponding parameters:

-   -   applicationData: (app data)    -   signingCertificate: (cert)*    -   signingPassword: (password)*    -   provisioningProfile: (profile)    -   callbackUrl:        http://mcs-tenant-a.internal:3000/maxbuild/complete?jobId=(BuildJobId)**        In this example, the certificate and the password are created by        the user of first device 602 exclusively for building mobile        application according to this embodiment (i.e., the certificate        and the password are not shared with services other than        building mobile application according to this embodiment), and        port 3000 is not publicly accessible.

Load balancer 616 maintains a list of healthy servers in server farm618. In one embodiment, this is done via a health check that performssanity checks at certain time intervals (e.g., every few minutes). Uponreceiving a build job request, load balancer 616 selects a server fromthe healthy server pool in the list and routes the build job request tothat server (e.g., routes the job to“http://mac-mini1.internal/build/initiate”). In one embodiment,selecting the server is according to a round robin process for buildjobs that are of equal complexity.

In one embodiment, a Tomcat web server is running on the selected serverin server farm 618. The Tomcat web server receives the build job requestand starts an external process that runs on an asynchronous servlet toprevent the input/output from blocking the request thread pool. When theprocess completes, the Tomcat web server creates a POST request to thecallback URL in the request payload. The following functionalityprovides an example payload for this new request:

-   -   result: (success if successful, etc)    -   binaryKey: (jobId)

MCS Portal VM 612 receives the new request and updates the correspondingrecord in the table of build jobs with the binary key from the payloadif the event has been successful. It also informs the client (i.e.,first device 602) that the build job was completed (e.g., via polling onOracle Business Intelligence Enterprise Edition (“OBIEE”) 11g push orasynchronous servlet with OBIEE 12c planned) and produces a QR code withan encoded link for downloading the application (e.g.,“https://mcs-tenant-a.cloud.oracle.com/max/native-application/(binaryKey)”).

Installing an Application

In one embodiment, once a user of second device 604 scans the QR code onsecond device 604, an “over the air” install is initiated. Scanning theQR code opens the URL encoded in the QR code (e.g.,“https://mcs-tenant-a.cloud.oracle.com/max/native-application/(binaryKey)”).Public OHS 606 receives the request, terminates the SSL, authenticatesand authorizes the user against OAM (assuming the user is logged in),places the user identity into the HTTP headers of the request, andforwards the request past firewall 608 to the WLS server of MCS PortalVM 612 (e.g., running at “http://mcs-tenant-a.internal/max/build”).

MCS Portal VM 612 receives the request, authorizes the user forprivileges against the requested application, determines user-agent (inthis context, the OS framework of the device, e.g., iOS vs Android) ofthe requesting device (second device 604), identifies the platform ofsecond device 604 (e.g., iOS), and forwards the request to acorresponding URL (e.g.,“https://mcs-tenant-a.cloud.oracle.com/max/native-application/plist/(binaryKey)”)by directing to Public OHS 606, which will in turn forward the requestto MCS Portal VM 612 to authorize (as performed during the build processdescribed herein to ensure that the user is allowed to download theapplication). MCS Portal VM 612 receives the forwarded request andgenerates a property list file (e.g., an iOS “p-list” file) thatincludes application information for a corresponding platform (e.g.,iPhone) as well as a link to the binary (e.g.,“https://mcs-tenant-a.cloud.oracle.com/max/native-application/ios/(binaryKey)”).

Second device 604 then prompts the user if they want to install theapplication. Assuming yes, second device 604 follows the link to thebinary (e.g.,“https://mcs-tenant-a.cloud.oracle.com/max/native-application/ios/(binaryKey)”)by directing to Public OHS 606 which will in turn forward the request toMCS Portal VM 612 to authorize (as performed during the build processdescribed herein to ensure that the user is allowed to download theapplication). MCS Portal VM 612 receives the request and generates a newbuild job request to build server farm 618 (e.g., at“http://max-mini-farm.internal/download/ios/(binaryKey)”) behind loadbalancer 616. Load balancer 616 selects a server in build server farm618 (e.g., via a round robin process) from a healthy server pool androutes the build job request to that server (e.g., to“http://mac-mini1.internal/download/ios/(binaryKey)”). An applicationserver (e.g., a Tomcat) on the selected server receives the request,determines if corresponding content exists, and streams the binary fromthe network (e.g., from“Filer/filer_mnt/generated_binaries/(binaryKey)/result.ipa”). Loadbalancer 616 returns the streamed response back to MCS Portal VM 612,which receives the response and copies it into its request's outputstream to second device 604. Finally, second device 604 receives thebinary and performs the install.

FIG. 7 is a block diagram of mobile security suite components in anembodiment that uses security services provided by a mobile securitysuite 700 such as OMSS. OMSS components are distributed across thecorporate DMZ 740 and the enterprise intranet (or corporate network750). Under OMSS, a security container 706 such as “Oracle MobileSecurity Container” from Oracle Corp. is installed on a mobile device702 and is configured to hold “containerized” applications 708, e.g.,applications that have been securely linked to their specific container.Mobile device 702 may also include other personal applications 704 heldoutside security container 706.

Security container 706 includes a secure web browser 712, a file manager(not shown), a document editor (not shown), and an optional securemobile mail manager 710. Secure mobile mail manager 710 includespersonal information management (“PIM”) applications such as a mailclient, calendar, contacts, tasks, and notes synchronizing withcorporate mail servers via the “Microsoft Exchange ActiveSync” (“EAS”)protocol. Many applications such as “Oracle Business Intelligence”(“BI”), “Oracle Fusion Tap,” “Oracle Social Network,” “Oracle EnterpriseManager Cloud Control,” “Oracle WebCenter Spaces,” etc., and a broadrange of third-party enterprise applications can be containerized withsecurity container 706. All data at rest inside containerizedapplications 708 on mobile device 702 is encrypted. Encrypted datastorage includes database, file store, cache, and user preferences.Security container 706 uses a secure channel such as an “AppTunnel” 714(as described in U.S. Pat. No. 8,332,464, the disclosure of which isincorporated herein in its entirety) to communicate with corporatenetwork 750 behind corporate DMZ 740. In one embodiment, data in transitthrough AppTunnel 714 is encrypted using TLS/SSL with FederalInformation Processing Standard (“FIPS”) approved algorithms.

In one embodiment, when a web browser or other client program makes anunauthenticated request to a security access server such as “OracleMobile Security Access Server” (“MSAS”) from Oracle Corp., the securityaccess server responds with a redirect to the appropriate securitycontainer. Security containers use a key hierarchy to protect data. Allkeys are derived from user credentials that are never stored. The keyhierarchy involves multiple keys to support different sensitivity ofdata. For example, a unique key is used for the user's authenticationcertificate, which is allowed to be open for a very short period oftime. A different key is used for the browser cache, which must remaindecrypted for an entire session. The main security container distributesand manages keys for the complete set of apps in the user's secureenterprise workspace.

Secure container 706 has at least three distinctive benefits overconventional mobile virtual private network (“VPN”) solutions: devicetrust vs. gateway, secure container password vs. device password, andsecure container AppTunnel vs. device-level VPN. OMSS extends anetwork's Kerberos authentication trust directly to the user's deviceinstead of stopping at a gateway server sitting in the DMZ. OMSS issignificantly more efficient and secure than implementing “constraineddelegation” offered by VPN providers. A constrained delegation solutionis not only less secure but also more cumbersome to set up and maintain.Further, the tradeoff between usability and security is magnified whendealing with consumer devices and BYOD programs. Corporate IT requiresstrong passwords to protect corporate data on BYOD devices. Conversely,users want simple passwords—or preferably no device password at all—sothey can easily access social networks and other consumer applications.Requiring a device password is frustrating for users, as they areconstantly using the device for non-enterprise purposes that don'trequire enterprise authentication. Embodiments provide the necessarybalance between security and usability when dealing with BYOD programsby requiring a password only to access corporate applications.

Yet further, device-level VPNs provide a trusted secure tunnel between auser's device and the enterprise's network. However, device-level VPNsolutions are more appropriate for corporate-owned and secured endpointdevices such as laptops than for consumer mobile devices. Once amobile-device VPN tunnel is open to the network, any application on adevice has access to this secure tunnel, causing significant securityvulnerability. With embodiments, however, the connection from mobiledevice 702 to enterprise intranet 750 exists only between securitycontainer 706 and enterprise servers.

In mobile security suite 700, MSAS 716 is typically deployed incorporate DMZ 740 and multiple server instances can be deployed behind aload balancer for high availability and scalability. MSAS 716 providestunneled connections between the server and containerized apps 708. MSAS716 brokers authentication (strong authentication leverages HTTPSconnections to “Oracle Access Manager” (“OAM”) 722 or Kerberosconnections to Kerberos Domain Controllers 718), authorizes, audits, andenables SSO for, and proxies requests to, their destination (resourcesin corporate intranet 750 such as web applications and web services724). MSAS 716 acts as the terminating end-point of the tunneledconnections initiated by security container 706 and containerizedapplications 708.

MSAS 716 supports “Oracle API Gateway” (“OAG”) from Oracle Corp. andOWSM from Oracle Corp. to add security, threat protection, andthrottling policies to an organization's REST API infrastructure. SSO issupported through OAuth, OAM tokens, Kerberos, and NT LAN Manager(“NTLM”). SAML is supported through OAM 722 or Kerberos integration withSAML identity providers such as Oracle, CA, or Ping Identity. MSAS 716is integrated with the OAM platform and supports the retrieval of OAMand OAuth tokens for SSO to backend resources protected by OAM, OAG, andOWSM. MSAS 716 also supports “virtual smart card” authentication byperforming public key infrastructure (“PKI”) authentication to MicrosoftActive Directory protected by a PIN. Digital certificates areprovisioned inside the security container app and only accessed aftersuccessful PIN validation. MSAS integration with OAM allows for contextaware, risk based, step-up authentication.

Mobile security suite 700 further implements OWSM which is a componentof the SOA Suite and addresses web-services-based SOA security andmanagement. The purpose of a SOA infrastructure is to allow consumers toinvoke services exposed by providers. OWSM offers a solution for policymanagement and security of such service infrastructure. It providesvisibility and control of the policies through a centralizedadministration interface offered by “Oracle Enterprise Manager” fromOracle Corp. OWSM allows companies to (1) centrally define and storedeclarative policies applied to the multiple web services making up aSOA infrastructure, (2) locally enforce security and management policiesthrough configurable agents, and (3) monitor runtime security eventssuch as failed authentication or authorization. It also providesbusiness agility to respond to security threats and security breaches byallowing policy changes to be enforced in real time without the need tointerrupt the running business processes.

Mobile security suite 700 further implements “Oracle Mobile SecurityManager” (“MSM”) 720 within corporate network 750. MSM 720 is a“WebLogic” managed server running on either Oracle Linux or Red HatEnterprise Linux. MSM 720 integrates with Microsoft Exchange Servers 728in corporate network 750 to provide access to corporate email services.MSM 720 also integrates with LDAP servers 732 to provision users, assignand manage policies for Mobile Device Management and for accessingsecurity container 706, manage the app catalog, control the remote lockor wipe of the device and secure workspace apps (wiping securitycontainer 706 removes all data and configuration for workspace apps),and set access control policies for the security container. Policies areassigned to users by associating policy templates with users and usergroups. Available policy controls include device restrictions,authentication (authentication frequency, failed attempt threshold, PINstrength for PKI), catalog (apps, URLs, file shares), container/apps(compromised platform, location services, offline status, inactivityduration, data leak prevention (“DLP”)), time access (lock if outsidetime window), Geo Access (lock if outside geo-fence (city, state,country)), devices (whitelist specific device models, specify minimum OSlevel), browser (disable address bar, disable download), file browser(allow/disallow, disable download, specify file server URL), personalinformation manager (“PIM,” mail server URL), provisioning (invitetemplate, PKI details), etc. If a user is in multiple groups and hasmultiple policies, policy combinations are resolved following specificrules.

MSM 720 maintains the EMM policies, which are then associated to one ormore user groups in the directory. MSM 720 does not perform any user orgroup management but leverages these identities and groups directly (nosynchronization) from the directory store. MSM 720 uses APNS and CGNover HTTPS to send notifications to devices. MSM 720 also exposes aWebDAV front-end to internal CIFS/SMB-enabled File Systems 730 or“Microsoft SharePoint servers,” and enables browsing intranet fileshares from the client.

With more and more organizations establishing a presence on socialnetworks, IT departments need support for social identities, which relyon more lightweight security standards than enterprise identities butare better adapted to the requirements of social networks. For example,some websites may require users to provide access tokens obtained fromFacebook or Google in order to be authenticated to their services.Accordingly, Mobile security suite 700 further implements OAMMS thatincludes a server that interfaces with existing backend identitymanagement infrastructures. The server acts as an intermediary betweensupported mobile client apps and backend identity services. Thisdecouples the client apps from the backend infrastructure so thatbackend infrastructure can be modified without having to update mobileclient programs. OAMMS includes the following functionality:

-   -   Delegated authorization leveraging the OAuth standard.    -   Mobile Services connecting browser-based (HTML5) and native        mobile apps to the enterprise identity management        infrastructure, typically the “Oracle Access Management        platform.”    -   Internet Identity Services that let OAMMS be used as the relying        party when interacting with popular, cloud-based identity        authentication and authorization services such as Google, Yahoo,        Facebook, Twitter, or LinkedIn. By deploying OAMMS, the user is        provided with multiple login options without the need to        implement access functionality for each identity provider        individually. User Profile Services providing a REST interface        for LDAP CRUD operations (customers use the same REST interface        to build graphical UIs for apps), user self service functions        such as self-registration, profile maintenance, password        management, and account deletion. User Profile Services are also        available as an OAuth resource.    -   Access Management Integration Services for leveraging OAM 722        through a runtime REST interface provided by an agent SDK.

FIG. 8 is a flow diagram of mobile application development in accordancewith embodiments of the present invention. In one embodiment, thefunctionality of the flow diagram of FIG. 8 (and FIG. 10 describedbelow) is implemented by software stored in memory or other computerreadable or tangible medium, and executed by a processor. In otherembodiments, the functionality may be performed by hardware (e.g.,through the use of an application specific integrated circuit (“ASIC”),a programmable gate array (“PGA”), a field programmable gate array(“FPGA”), etc.), or any combination of hardware and software. An exampleof cloud based mobile application development is provided in U.S.Provisional App. No. 62/186,080 (Attorney Docket No.: 88325-924721(165701US), Client Reference No.: ORA150600-US-PSP), filed Jun. 29,2015, entitled “CLOUD BASED EDITOR FOR GENERATION OF INTERPRETEDARTIFACTS FOR MOBILE RUNTIME,” the disclosure of which is herebyincorporated by reference.

At 810 an application definition wizard is generated. An applicationdefinition wizard as used herein represents a set of one or more UIsthat guide a user during the definition process of a mobile applicationthat utilizes one or more pre-defined cloud-accessible services. Theapplication definition wizard can implement one or more workflows eachassociated with a part of the application definition process. In oneembodiment, the application definition wizard can prompt or otherwiseguide a user to specify application defaults, such as applicationidentifier prefixes, default icons, splash screens, defaultapplication/feature templates, setup enterprise provisioningprofile/keystore, or the like.

In certain embodiments, the application definition wizard can prompt orotherwise guide a user to specify an application name, a form factor(such as a phone or tablet device), a navigation type (e.g., nonemeaning a single feature or UI, as springboard, a navigation bar(“NavBar”), a Spring/Nav combo, or the like), and any applicationpreferences.

At 820 an application definition is received. As discussed herein, theapplication definition can include any information needed in order tocreate at least a minimally functional mobile application. At 830 amobile application is generated based on the application definition. Inone embodiment, the mobile application is represented in a simulator ofthe target device and can include a set of definitions that wheninterpreted, function as a compiled mobile application.

At 840 a feature selection wizard is generated. A feature selectionwizard as used herein represents a set of one or more UIs that guide auser during the development process of a mobile application thatutilizes one or more pre-defined cloud-accessible services. The featureselection wizard can implement one or more workflows each associatedwith a part of the application development process. In one embodiment,the feature selection wizard can prompt or otherwise guide a user tospecify features, UI modules, Business Object, or the like that can beused with the mobile application.

In certain embodiments, the feature selection wizard can prompt orotherwise guide a user to specify components of the first screen of themobile application. A component can be selected from a catalog ofcomponents.

In certain embodiments, the feature selection wizard can prompt orotherwise guide a user to specify components of other screens of themobile application. These other screens can form part of one or more UImodules. In certain embodiments, the feature selection wizard can promptor otherwise guide a user to specify one or more UI modules of themobile application. A UI module represents a processor, task, or flowthat can be performed with respect to the mobile application. A UImodule can be selected from a catalog of UI modules or a set oftemplates that provide cohesive collections of UI elements and pageflows. Some examples of UI modules are approval workflows, worker tasks,data entry tasks, reports builders, or the like. A template provides apre-set arrangement/binding of a set of UI elements so that a user onlyneeds to configure those UI elements and bind the template instead ofhaving to arrange and bind individual UI elements. In one embodiment, auser may contribute their own templates to the set of templatesavailable to another user. The user can configure or otherwise specify aseries of pages that represent the UI Module. For each page, the usercan be presented with a set of layout templates much like before. Eachlayout template might have several facets such as choosing a secondarytemplate.

In some embodiments, the feature selection wizard can prompt orotherwise guide a user to specify additional features of the mobileapplication, such as business objects previously defined. The user canspecify what resource of the backend service, API, or connector is to beused or otherwise associated with UI elements of each component, screen,UI module, or the like.

At 850 feature definitions are received, and at 860 a data bindingwizard is generated. A data binding wizard as used herein represents aset of one or more UIs or UI elements of an existing UI that guide auser during the data binding process of a mobile application thatutilizes one or more pre-defined cloud-accessible services. The databinding wizard can implement one or more workflows each associated witha part of the application development process. In one embodiment, thedata binding wizard can prompt or otherwise guide a user to specify howfeatures, screens, UI modules, etc., are bound to business objects,services, APIs, or the like that can be used with the mobileapplication. In certain embodiments, the data binding wizard can promptor otherwise guide a user to specify a business object of the mobileapplication. A business object can be selected from a catalog or set ofservices, APIs, etc. that are available to the mobile application.

At 870 data binding definitions are received. In various embodiments,steps 840-870 can be performed in series or in parallel. Individualsteps in 840-870 can be performed on individual element of a mobileapplication or to a group of elements. As illustrated, a user can repeatthe process of feature definition and data binding to create a mobileapplication.

At 880 the mobile application is deployed. The user can test theapplication using a testing application deployed on a target device, oras a native application deployed on a target device.

Discovery of Federated Logins

In some current cloud systems, there is a different login server foreach company that subscribes to a cloud service. That is, each companyhas a unique login server attached to their service, and employees ofeach company need to log into their corresponding login server.Accordingly, discovery of the appropriate login server and logging intoit is required prior to interacting with a cloud service.

Some known systems provide applications that require the user to type inthe URL of the unique login server that needs to be logged into. Anexample of such applications is Oracle CRM from Oracle Corp. However,requiring the user to type in this URL is error prone. Further, suchrequirement may result in an unpleasant user experience.

Some known systems provide applications that determine theircorresponding unique login server based on a user company email address.For example, for a user company email address of “user@acme.com,” thecorresponding unique login server may be mapped to“acme.mycloudservice.com.” An example of such applications is WebEx fromCisco Corp. Determining the unique login server based on a company emailaddress may be performed by accessing a centralized repository thatprovides a mapping between company emails and corresponding unique loginservers. However, having such a centralized repository may not always bepossible in a cloud system, for example, when a cloud backend does notallow federation of user credentials in SSO systems and/or when securityis internal only and the cloud system is not able to authenticate withthird party sources.

Some known systems install a provisioning profile on a mobile device sothat the provisioning profile can then tell the other applications howto locate services for the mobile device. A provisioning profileincludes a set of metadata that an application can use to determinedefault services. For example, a provisioning profile may include thelink to a login server as part of the metadata. In these known systems,the user needs to download and install the provisioning profile (whichmay be distributed by their company). However, many customers do notwish to install company profiles, especially on personal devices.Further, these provisioning profiles need to be sent to users as aseparate process.

Some known systems integrate with SSO which provides access control ofmultiple related but independent software systems. SSO is a form offederated identity management which pertains to the implementation of acommon set of policies, practices, and protocols to manage electronicidentity and trustworthiness of users and devices across organizations.These known systems need to have a priori knowledge of a number ofcompanies so that a user can specify one of those companies to sign on.However, not every system is integrated with SSO, for example, due tolimitations of the cloud backend.

In contrast to the known systems, embodiments provide federated logindiscovery functionality at the same time as downloading resources to auser device. In one embodiment, the unique login server of a company isautomatically discovered as the user follows a download link. The useris then asked to login and the resource is subsequently downloaded tothe mobile device of the user. Embodiments do not require any specialsetup on cloud service authentication systems, thus allowing for workingwith any identity store for security. Further, embodiments do notrequire a user to type in the address of a login server or use aseparate discovery service to login, and the functionality of afederated login is hidden from the user. Accordingly, embodimentsimprove user experience. Embodiments are applicable to any corporatenative applications that require a user to identify their company.

In one embodiment, a user receives a download link from a service todownload a resource. An example of such resource is the metadata thatdescribes an application developed via a web-based framework. Thedownload link may be received via any communication or networking means,e.g., email, text message, social networks, etc. If the user follows thedownload link from a desktop browser, they are presented with a QR codethat they can scan with their mobile device. Alternatively, if the useris on a mobile device and follows the download link, they are presentedwith a button to download the content. After scanning the QR code orclicking the button (depending on how the user opened the link), theuser is asked for login credentials. The resource is then downloaded andcan be forwarded to an application on the user device.

In one embodiment, the link that is sent to the user includes a specificcompany service URL which is unprotected (i.e., no login is required tofollow the company service URL) and includes an ID or locator of theresource the user wishes to download. An example of such URL is:

-   -   max://?loginHost=server.oraclecloud.com&app=appId        where the “loginHost” parameter describes the server host to        connect to. If the user follows the company service URL from a        non-mobile device (e.g., a desktop computer), the user is        presented with a screen that includes some information about the        resource as well as a QR code. The user can then download the        content by scanning the QR code using a scanning application on        a mobile device. Alternatively or additionally, QR scanning        functionality can be built into applications that are configured        to receive the downloaded content.

The same company service URL is also provided to a user to follow from amobile device, but the screen that is provided on the mobile device uponfollowing the company service URL includes some information about theresource, and a download button instead of a QR code. Although the sameURL is provided to users of mobile and non-mobile devices, embodimentsdetect if the user is using a mobile device or a non-mobile device andprovide respective content accordingly.

In one embodiment, the link for the company service URL as configured tobe opened on both mobile and non-mobile devices is encoded in a URIschema. A URI schema is a mechanism to trigger actions upon clicking ona link. In one embodiment, the URI schema allows native applications tointercept a request (e.g., the request corresponding to clicking on alink). The content encoded in this schema includes the login serveraddress and the address of the downloadable content, where thedownloadable content is protected by login functionality and cannot beaccessed directly. Upon following a tokenized URL that implements theURI schema, the receiving application (the application that interceptsthe request from the URI schema) identifies the login server from theencoded information in the URI schema, lets the user login, and thendownloads/installs the new application.

In one embodiment, when an address entered in a web browser running on amobile device includes embedded tokens indicating an applicationdeveloped by a web-based framework (e.g., by Oracle MAF), its logininformation, application download location information, backends used bythe application, etc., the corresponding URI schema is configured toensure that these tokens are obtained by the OS of the mobile device andforwarded to an application on the device that is configured to receivethe downloaded content.

An example of such URL is:

-   -   max://?loginHost=server.oraclecloud.com&backendId=someBackendId&app=someAppId        which includes the embedded tokens of        “loginHost=server.oraclecloud.com” (indicating login server        information), “backendId=someBackendId” (indicating backend        information), and “app=someAppId” (indicating application        information). In this example, a mobile application can        intercept URLs with “max” as their schema (e.g., the first part        of the URL) and forward them to an application that is        configured to handle these URL and extract the embedded tokens.

FIG. 9 is an example application network topology 900 for web-basedapplication development in one embodiment. This embodiment providesnative application development functionality that is applicable to usecases such as running “published” applications, sharing applicationsbuilt in a web-based framework with other mobile users who may not havean account in the web-based framework, deploying applications forcompanies that do not wish to share enterprise keys (where keys arerequired for a full build service), etc. In this embodiment, a hostingapplication on a user device 912 allows a user to download hostedapplications (built in the web-based framework) as added features to thehosting application. The hosting application may be downloaded on userdevice 912 from, e.g., AppStore, Google play, etc. The hostedapplications are lightweight and do not require building nativeartifacts, thus providing an alternative to using a build server farm.

Application network topology 900 implements MCS “team member” loginfunctionality 926 which provides cookie-based login for users 928 thatdevelop applications. After logging in, users 928 may developapplications by communicating with an MCS portal virtual machine 914through OHS WebGate 924 (the web-server plug-in for Oracle AccessManager (“OAM”) to intercept HTTP requests and forward them to an accessserver for authentication and authorization).

An authentication cookie is an item in a dictionary of items each havinga key (e.g., “username”) and a value (e.g., an instance of a usernamesuch as “bob123”). When a browser sends a request to a website,automatic authentication can be performed by including authenticationcookies in the request so the cookies can be checked by a host server. Acookie may be set by adding it to the response the server sends back tothe requesting browser which then adds (saves) the cookie upon receivingthe response. Thereafter the browser adds the cookies in the HTTP headerof every request made to that server.

In one embodiment, MCS portal virtual machine 914 includes an MCS UIcluster 918 that in turn includes a UI server 920 of the web-basedframework and MCS tooling functionality 922. In this embodiment, users928 can use MCS tooling functionality 922 to select a cloud or otherconnector to a backend system of interest and then develop anapplication. The mobile backends that support the application may run onan MCS runtime test virtual machine 902 in a runtime test environment oran MCS runtime production virtual machine 904 in a runtime productionenvironment. The runtime production virtual machine 904 may includeJavaScript MCS services 908 accessible via an MCS core runtime cluster906.

Application network topology 900 further implements MCS mobile userruntime login functionality 910 which allows the hosting application onuser device 912 to log into MCS as a mobile user. The hostedapplications can then use MCS mobile user basic access authentication(or “basic auth,” a method for an HTTP user agent to provide a usernameand password when making a request). In one embodiment, the logins arestored indefinitely on mobile device 912 and shared across the hostedapplications.

In one embodiment, when an application is developed in applicationnetwork topology 900, UI server 920 of the web-based framework hosts theHTML page that is generated for the developed application. The HTML pageincludes a QR code that points to one of the environments (e.g.,test/production) which communicates with UI server 920 to obtain andcache application data. Once this data is cached on one of theenvironments, it can be provided to users (e.g., mobile device 912) bythat environment without needing to obtain it again from UI server 920.In one embodiment, the QR code will only show up on desktop browsers,and if a mobile user looks at the same page, they will instead see an“Install” button that when clicked will follow the same URL as encodedin the QR code. Accordingly, by allowing for obtaining application datafrom one of the environments instead of accessing UI server 912,embodiments prevent the situation where a large number of users accessUI server 912. In one embodiment, a download service 916 within MCSportal virtual machine 914 serves and stores application data and allowsfor lightweight declarative metadata to be downloaded onto mobile device912. This metadata is the application metadata and can be run in thehost application by having the host application interpret and executethe metadata. In one embodiment, an application download service can beused in a test environment for application testing and in a productionenvironment for application production.

Accordingly, the information that is sent down to mobile device 912 forinstalling a hosted application is declarative data that getsinterpreted on mobile device 912 during runtime, and binary files of thehosting application include the codes necessary for running the hostedapplication. The hosted applications also share the same login. Forexample, within a same hosting application, a hosted application forenterprise HR functionality and another hosted application attached tothe CRM of the enterprise may share the same login. In one embodiment,once a new hosted application is downloaded, a corresponding icon isadded to a springboard of the hosting application on mobile device 912.The new hosted application can then be modified, upgraded, and/oruninstalled independently of other hosted applications within thehosting application.

In one embodiment, the URL encoded by the QR code or linked from thedownload button (depending on whether being viewed from a desktopbrowser or a mobile device) includes the login server information.Accordingly, embodiments do not attempt to login a user at the time ofstarting an application (since required login information is notavailable at that time), but instead attempt to login the user at thefirst time the application is downloaded (e.g., via a QR code or adownload button), which is when the login server information isavailable.

FIG. 10 is an example application sharing flow 1000 in one embodiment.At 1002 a user “Bob” that develops an application and wishes to publishit gets a “share” link from a web-based framework for the publishedapplication. The user may be provided with this share link in a screenthat includes a list of several applications. Each application in thelist may be presented as a “card” which can be flipped over to reveal aQR code for the application. The card may also include a share button,and upon clicking on the share button, a link is provided for sharingthe application.

At 1004 the user sends the share link to prospective mobile users of theapplication. The share link may be shared with mobile users via anynetworking, communication, or sharing service such as social networks,email, instant message, etc. In one embodiment, the share link is not alink to the application but a link to an HTML page which includesinformation related to the application. This information may include,for example, screens/previews of the application, applicationinformation, instructions for using the application, a QR code forlaunching the application (if the link is reached via a non-mobiledevice), an “install” button for launching the application (if the linkis reached by a mobile device), etc. Accordingly, users that receive thelink may use it to download the application created in the web-basedframework. This application is secured with MCS “mobile user”credentials. However, the users do not need to know the domain of theMCS server, since both login and application download links areincluded/encoded within the share link.

If a mobile user receives the share link and opens it on a non-mobiledevice (e.g., a desktop computer) at 1006, at 1008 the user sees anapplication landing page including a QR code that can be scanned by amobile device. Upon scanning the QR code, at 1014 the informationencoded in the share link is used to log in the mobile user into MCSruntime, and at 1016 the application is downloaded to the mobile devicethat scanned the QR code.

If a mobile user receives the share link and opens it on a mobile device(e.g., a mobile phone) at 1010, at 1012 the user sees an applicationlanding page including a button for installing the application. Uponclicking the button on the mobile device, at 1014 the informationencoded in the share link is used to log in the mobile user into MCSruntime, and at 1016 the application is downloaded to the mobile device.

FIG. 11 is a flow diagram of federated login discovery functionality inaccordance with embodiments of the present invention.

At 1110 download location information is included in an unprotected URL,where the download location information identifies a download locationfor downloading an application provided by a cloud system.

At 1120 login server information is included in the unprotected URL,where the login server information identifies a login server that isconfigured to be logged in before downloading the application from thedownload location. In one embodiment, based on the unprotected URL, theapplication is downloaded on a mobile device from the download locationand after logging into the login server.

In one embodiment, the application may be developed by accessing aweb-based application development server in the cloud system. After theapplication is developed, the web-based application development servergenerates the unprotected URL.

In one embodiment, the unprotected URL is shared with one or moredevices for downloading the application. The one or more devices mayinclude a non-mobile device, and following the unprotected URL on thenon-mobile device opens a web page that includes download informationfor the application. The web page includes a QR code that encodes theapplication and the login information, and the application is downloadedto the mobile device that scans the QR code.

In one embodiment, the one or more devices includes the mobile device,and following the unprotected URL on the mobile device opens a web pagethat includes download information for the application. The web pageincludes a download button for downloading the application, and clickingthe download button downloads the application to the mobile device.

In one embodiment, the unprotected URL is a tokenized URL that includestokens for at least one of an application link, application logininformation, application download information, and a mobile backend usedby the application.

In one embodiment, logging into the login server includes authenticatinga device based on user credentials provided through the device, and theapplication is installed on the device when the device is authenticated.In one embodiment, the device includes a hosting application, and theapplication is installed as a feature of the hosting application.

In one embodiment, installing the application is performed bydownloading declarative metadata of the application to the device, andthe declarative metadata of the application is interpreted at runtime.In one embodiment, the application shares login information with otherapplications that are installed as features of the hosting application.In one embodiment, each application that is added as a feature of thehosting application is configured to be independently modified.

As disclosed, embodiments provide login discovery functionality fordownloading an application. In one embodiment, login server informationis encoded within a tokenized URL that is provided to a user fordownloading an application. Upon following the URL, the embodiment logsinto the appropriate log in server and downloads the application.Accordingly, by simplifying login discovery and hiding it from the user,embodiments improve user experience. Further, embodiments do not requireany special setup on cloud service authentication systems, thus allowingfor working with any identity store for security.

Several embodiments are specifically illustrated and/or describedherein. However, it will be appreciated that modifications andvariations of the disclosed embodiments are covered by the aboveteachings and within the purview of the appended claims withoutdeparting from the spirit and intended scope of the invention.

What is claimed:
 1. A computer readable medium having instructionsstored thereon that, when executed by a processor, cause the processorto: include download location information in an unprotected UniformResource Locator (URL), wherein the download location informationidentifies a download location for downloading an application providedby a cloud system; and include login server information in theunprotected URL, wherein the login server information identifies a loginserver that is configured to be logged in before downloading theapplication from the download location, wherein, based on theunprotected URL, the application is configured to be downloaded on amobile device from the download location and after logging into thelogin server.
 2. The computer readable medium of claim 1, wherein theapplication is developed by accessing a web-based applicationdevelopment server in the cloud system.
 3. The computer readable mediumof claim 2, wherein, after the application is developed, the web-basedapplication development server generates the unprotected URL.
 4. Thecomputer readable medium of claim 3, wherein the unprotected URL isshared with one or more devices for downloading the application.
 5. Thecomputer readable medium of claim 4, wherein the one or more devicesinclude a non-mobile device, wherein following the unprotected URL onthe non-mobile device opens a web page that includes downloadinformation for the application.
 6. The computer readable medium ofclaim 5, wherein the web page includes a Quick Response (QR) code thatencodes the application and the login information, wherein theapplication is downloaded to the mobile device that scans the QR code.7. The computer readable medium of claim 4, wherein the one or moredevices includes the mobile device, wherein following the unprotectedURL on the mobile device opens a web page that includes downloadinformation for the application.
 8. The computer readable medium ofclaim 7, wherein the web page includes a download button for downloadingthe application, wherein clicking the download button downloads theapplication to the mobile device.
 9. The computer readable medium ofclaim 1, wherein the unprotected URL is a tokenized URL that includestokens for at least one of an application link, application logininformation, application download information, and a mobile backend usedby the application.
 10. The computer readable medium of claim 1, whereinlogging into the login server includes authenticating a device based onuser credentials provided through the device.
 11. The computer readablemedium of claim 10, wherein the application is installed on the devicewhen the device is authenticated.
 12. The computer readable medium ofclaim 11, wherein the device includes a hosting application, wherein theapplication is installed as a feature of the hosting application. 13.The computer readable medium of claim 12, wherein installing theapplication is performed by downloading declarative metadata of theapplication to the device.
 14. The computer readable medium of claim 13,wherein the declarative metadata of the application is interpreted atruntime.
 15. The computer readable medium of claim 12, wherein theapplication shares login information with other applications that areinstalled as features of the hosting application.
 16. The computerreadable medium of claim 12, wherein each application that is added as afeature of the hosting application is configured to be independentlymodified.
 17. A method comprising: including download locationinformation in an unprotected Uniform Resource Locator (URL), whereinthe download location information identifies a download location fordownloading an application provided by a cloud system; and includinglogin server information in the unprotected URL, wherein the loginserver information identifies a login server that is configured to belogged in before downloading the application from the download location,wherein, based on the unprotected URL, the application is configured tobe downloaded on a mobile device from the download location and afterlogging into the login server.
 18. The method of claim 17, wherein theapplication is developed by accessing a web-based applicationdevelopment server in the cloud system.
 19. The method of claim 18,wherein, after the application is developed, the web-based applicationdevelopment server generates the unprotected URL.
 20. A systemcomprising: a cloud system; a login server; and a mobile device, whereindownload location information is included in an unprotected UniformResource Locator (URL), wherein the download location informationidentifies a download location for downloading an application providedby the cloud system, wherein login server information is included in theunprotected URL, wherein the login server information identifies thelogin server that is configured to be logged in before downloading theapplication from the download location, wherein, based on theunprotected URL, the application is configured to be downloaded on themobile device from the download location and after logging into thelogin server.